Remote MCP · Endpoint

AIData.Broker MCP server

No. AIData.Broker answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://aidata.broker/mcp

The last check completed an MCP handshake.

Registry name
broker.aidata/market
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
90 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Gets companies' data to the AI buyers that pay for it: prices, buyers, deals and a free valuation.
Listing
From the official MCP registry (active).
Recent checks of AIData.Broker
CheckedResultHandshake
7 hours agoHandshake completed90 ms
4 days agoHandshake completed102 ms
14 days agoHandshake completed85 ms
15 days agoHandshake completed158 ms
15 days agoHandshake completed178 ms
17 days agoHandshake completed204 ms
18 days agoHandshake completed93 ms
19 days agoHandshake completed5.29 s
20 days agoHandshake completed5.36 s
21 days agoHandshake completed98 ms
23 days agoHandshake completed112 ms
26 days agoHandshake completed97 ms
28 days agoHandshake completed90 ms

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

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