Attention Trends
dev.workers.shopttyass-85f.attention-trends/attention-trendsattention-trends.shopttyass-85f.workers.devstreamable-httpv0.2.0Scanned
Topic popularity, interest over time and trending topics from Wikipedia pageviews (x402 paid).
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 2Claude Code: ask
trending_topicsWhat is trending right now: the most-read Wikipedia articles for a language and day (default yesterday UTC), with views and rank, cleaned of the Main Page, special and other non-ar…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it What is trending right now: the most-read Wikipedia articles for a language and day (default yesterday UTC), with views and rank, cleaned of the Main Page, special and other non-article pages. A daily signal of trending topics, breaking news and current events in 300+ Wikipedia language editions. Suited to trend discovery, news monitoring and content ideas. Paid: $0.005 USDC per call via x402.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
wikipedia_pageviews_trendWikipedia pageviews trend for any topic: interest over time as a measure of topic popularity and public attention.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Wikipedia pageviews trend for any topic: interest over time as a measure of topic popularity and public attention. Free text (brand, person, product, event) is resolved to the matching Wikipedia article. Returns daily views normalized 0-100, 7-day and window % change, direction (rising, falling, stable, spiking), peak day and spike detection. Similar in purpose to Google Trends search interest, but it measures Wikipedia reading, not searches. Paid: $0.005 USDC per call via x402.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
Only reads 1Show 1 read-only tool
compare_topic_popularityCompare the popularity of 2-5 topics (brands, competitors, products, people, keywords) by Wikipedia pageviews.Reads text others writeNo findings
Why it is in this group
- The name "compare_topic_popularity" says "compare": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Compare the popularity of 2-5 topics (brands, competitors, products, people, keywords) by Wikipedia pageviews. Returns one jointly normalized 0-100 interest-over-time series per topic, share of attention, the most popular and the fastest-rising topic, and per-topic trend direction and spikes. A Google-Trends-style popularity comparison based on Wikipedia reading rather than searches. Suited to competitor analysis, brand tracking and content planning. Paid: $0.01 USDC per call via x402.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http attention-trends https://attention-trends.shopttyass-85f.workers.dev/mcpclaude mcp add --transport http attention-trends https://attention-trends.shopttyass-85f.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__attention-trends__compare_topic_popularity"
],
"ask": [
"mcp__attention-trends__wikipedia_pageviews_trend",
"mcp__attention-trends__trending_topics"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as attention-trends. Review it before you use it.
Capability tags behind 3 rules
- mcp__attention-trends__wikipedia_pageviews_trend untrusted-input
- mcp__attention-trends__compare_topic_popularity untrusted-input
- mcp__attention-trends__trending_topics untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/dev.workers.shopttyass-85f.attention-trends/attention-trends/verify?hash=41593013375d2c644919effad690921cb85f71dd67af4bb7109cc256f15a9b1a" | jq -e '.changed == false'Pinned hash 41593013375d, from Oct 22, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/dev.workers.shopttyass-85f.attention-trends/attention-trends/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/dev.workers.shopttyass-85f.attention-trends/attention-trends)Source: MCP Registry. Synced Oct 22, 2026, 16:17 UTC.