Remote MCP · Endpoint

Agent Data Co MCP server

No. Agent Data Co answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://agentdataco.com/mcp

The last check completed an MCP handshake.

Registry name
com.agentdataco/api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
78 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Daily AI-ecosystem data: GitHub AI/MCP repos, MCP registry, HF trending, LLM pricing, with history.
Listing
From the official MCP registry (active).
Recent checks of Agent Data Co
CheckedResultHandshake
13 minutes agoHandshake completed78 ms
10 days agoHandshake completed94 ms
10 days agoHandshake completed142 ms
11 days agoHandshake completed123 ms
13 days agoHandshake completed248 ms
14 days agoHandshake completed94 ms
14 days agoHandshake completed101 ms
15 days agoHandshake completed266 ms
17 days agoHandshake completed90 ms
19 days agoHandshake completed70 ms
21 days agoHandshake completed106 ms
24 days agoHandshake completed173 ms
26 days agoHandshake completed103 ms
28 days agoHandshake completed54 ms

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

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 Co and makes no claim about it beyond what these checks measured.