Remote MCP · Endpoint

Attention Trends MCP server

No. Attention Trends answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://attention-trends.shopttyass-85f.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.shopttyass-85f.attention-trends/attention-trends
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
60 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Topic popularity, interest over time and trending topics from Wikipedia pageviews (x402 paid).
Listing
From the official MCP registry (active).
Recent checks of Attention Trends
CheckedResultHandshake
34 minutes agoHandshake completed60 ms
3 days agoHandshake completed271 ms
13 days agoHandshake completed74 ms
13 days agoHandshake completed310 ms
15 days agoHandshake completed218 ms
16 days agoHandshake completed225 ms
17 days agoHandshake completed83 ms
18 days agoHandshake completed259 ms
18 days agoHandshake completed217 ms
20 days agoHandshake completed531 ms
22 days agoHandshake completed502 ms
25 days agoHandshake completed69 ms
27 days agoHandshake completed330 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Attention Trends and makes no claim about it beyond what these checks measured.