Remote MCP · Endpoint

CompanyData MCP server

No. CompanyData answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://companydata.com/mcp/

The last check completed an MCP handshake.

Registry name
com.companydata/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
233 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Company search and enrichment from official business registers in 200+ countries.
Listing
From the official MCP registry (active).
Recent checks of CompanyData
CheckedResultHandshake
2 hours agoHandshake completed233 ms
1 day agoHandshake completed212 ms
2 days agoHandshake completed252 ms
2 days agoHandshake completed554 ms
4 days agoHandshake completed485 ms
7 days agoHandshake completed199 ms
9 days agoHandshake completed226 ms
12 days agoHandshake completed585 ms
14 days agoHandshake completed207 ms
16 days agoHandshake completed206 ms
18 days agoHandshake completed531 ms
20 days agoHandshake completed185 ms
22 days agoHandshake completed561 ms
23 days agoHandshake completed613 ms

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

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