Attention Trends
REMOTE · ATTENTION-TRENDS.SHOPTTYASS-85F.WORKERS.DEV
Topic popularity, interest over time and trending topics from Wikipedia pageviews (x402 paid).
Available components
Last scanned (2 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 643 tokens (~214/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://attention-trends.shopttyass-85f.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shopttyass-85f.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 53a1cc87193825426d166f950da7e8afa6e |
| SANs: *.shopttyass-85f.workers.dev, shopttyass-85f.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of attention-trends.shopttyass-85f.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://attention-trends.shopttyass-85f.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://attention-trends.shopttyass-85f.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_topic_popularity Compare Topic Popularity ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window length in days, ending yesterday UTC (default 30) |
| lang | string | – | Wikipedia language code, e.g. 'en', 'fr', 'de', 'ja' (default en) |
| topics | string | yes | 2-5 comma-separated topics, e.g. 'ChatGPT,Claude,Gemini' |
No output schema declared.
No examples provided.
trending_topics Trending Topics (Wikipedia) ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Day YYYY-MM-DD (default: yesterday UTC) |
| lang | string | – | Wikipedia language code, e.g. 'en', 'fr', 'de', 'ja' (default en) |
| limit | integer | – | Number of articles (default 25) |
No output schema declared.
No examples provided.
wikipedia_pageviews_trend Wikipedia Pageviews Trend ~198
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window length in days, ending yesterday UTC (default 30) |
| lang | string | – | Wikipedia language code, e.g. 'en', 'fr', 'de', 'ja' (default en) |
| topic | string | yes | Free-text topic resolved to the best-matching Wikipedia article, e.g. 'bitcoin', 'Taylor Swift', 'AI Act' |
No output schema declared.
No examples provided.
How do I install the Attention Trends MCP server?
Attention Trends is a hosted endpoint at https://attention-trends.shopttyass-85f.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · attention-trends.shopttyass-85f.workers.dev
claude mcp add --transport http dev-workers-shopttyass-85f-attention-trends-atte 'https://attention-trends.shopttyass-85f.workers.dev/mcp'
What is the Attention Trends MCP server?
Attention Trends is an MCP server listed in the public MCP registry as dev.workers.shopttyass-85f.attention-trends/attention-trends. Topic popularity, interest over time and trending topics from Wikipedia pageviews (x402 paid). This page covers its hosted endpoint (https://attention-trends.shopttyass-85f.workers.dev/mcp).
Is the Attention Trends MCP server safe to use?
Attention Trends scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Attention Trends MCP server expose?
Attention Trends exposes 3 tools: wikipedia_pageviews_trend, compare_topic_popularity, trending_topics. Their descriptions and schemas cost roughly 538 tokens of context every time the server is loaded.
Does the Attention Trends MCP server require authentication?
No. We connected to Attention Trends without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Attention Trends MCP server still maintained?
Attention Trends is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.