Remote MCP · Endpoint

Agent Data Broker MCP server

No. Agent Data Broker answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.carpdroid-commits/agent-data-broker
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
62 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Company enrichment + SEC EDGAR filings, financials, insider trades for agents; $0.01 USDC via x402
Listing
From the official MCP registry (active).
Recent checks of Agent Data Broker
CheckedResultHandshake
33 minutes agoHandshake completed62 ms
3 days agoHandshake completed151 ms
13 days agoHandshake completed192 ms
13 days agoHandshake completed202 ms
15 days agoHandshake completed192 ms
16 days agoHandshake completed194 ms
17 days agoHandshake completed179 ms
18 days agoHandshake completed271 ms
18 days agoHandshake completed185 ms
20 days agoHandshake completed454 ms
22 days agoHandshake completed378 ms
25 days agoHandshake completed159 ms

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

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