Remote MCP · Endpoint

CompanyGraph MCP server

No. CompanyGraph answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.companygraph.io/mcp

The last check completed an MCP handshake.

Registry name
io.companygraph/mental-model
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
273 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
CompanyGraph: Written once, read by both
Listing
From the official MCP registry (active).
Recent checks of CompanyGraph
CheckedResultHandshake
1 hour agoHandshake completed273 ms
2 days agoHandshake completed168 ms
4 days agoHandshake completed275 ms
5 days agoHandshake completed167 ms
7 days agoHandshake completed315 ms
8 days agoHandshake completed166 ms
9 days agoHandshake completed275 ms
12 days agoHandshake completed275 ms
13 days agoHandshake completed179 ms
15 days agoHandshake completed274 ms
16 days agoHandshake completed292 ms
18 days agoHandshake completed170 ms
19 days agoHandshake completed195 ms
20 days agoHandshake completed175 ms
20 days agoHandshake completed290 ms
21 days agoHandshake completed169 ms
22 days agoHandshake completed288 ms

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