Remote MCP · Endpoint

Agent Data API MCP server

No. Agent Data API answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://agent-data.centorprat.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.Bustlll/agent-data-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
187 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Memecoin screener, backtests, exit alerts, wallet traces + web search, enrichment, 50+ tools (x402)
Listing
From the official MCP registry (active).
Recent checks of Agent Data API
CheckedResultHandshake
37 minutes agoHandshake completed187 ms
4 days agoHandshake completed678 ms
7 days agoHandshake completed180 ms
16 days agoHandshake completed483 ms
16 days agoHandshake completed535 ms
18 days agoHandshake completed192 ms
19 days agoHandshake completed322 ms
20 days agoHandshake completed313 ms
21 days agoHandshake completed201 ms
22 days agoHandshake completed582 ms
23 days agoHandshake completed343 ms
26 days agoHandshake completed313 ms
29 days agoHandshake completed401 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 Agent Data API and makes no claim about it beyond what these checks measured.