Remote MCP · Endpoint

GuestGraph MCP server

No. GuestGraph answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.guestgraph.io/mcp

The last check completed an MCP handshake.

Registry name
io.guestgraph/mental-model
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
283 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
GuestGraph: One guest, not five strangers
Listing
From the official MCP registry (active).
Recent checks of GuestGraph
CheckedResultHandshake
1 hour agoHandshake completed283 ms
2 days agoHandshake completed168 ms
4 days agoHandshake completed278 ms
6 days agoHandshake completed175 ms
7 days agoHandshake completed289 ms
9 days agoHandshake completed311 ms
10 days agoHandshake completed294 ms
11 days agoHandshake completed561 ms
14 days agoHandshake completed277 ms
15 days agoHandshake completed179 ms
17 days agoHandshake completed281 ms
18 days agoHandshake completed359 ms
19 days agoHandshake completed174 ms
20 days agoHandshake completed288 ms
21 days agoHandshake completed277 ms
21 days agoHandshake completed278 ms

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