Remote MCP · Endpoint

GraphOS MCP Server MCP server

No. GraphOS MCP Server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.apollographql.com/

The last check completed an MCP handshake.

Registry name
io.github.apollographql/graphos-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
47 ms
Tools exposed
32 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search Apollo docs, specs, and best practices
Listing
From the official MCP registry (active).
Recent checks of GraphOS MCP Server
CheckedResultHandshake
1 hour agoHandshake completed47 ms
2 days agoHandshake completed47 ms
4 days agoHandshake completed76 ms
5 days agoHandshake completed41 ms
7 days agoHandshake completed68 ms
8 days agoHandshake completed45 ms
9 days agoHandshake completed55 ms
12 days agoHandshake completed64 ms
13 days agoHandshake completed50 ms
15 days agoHandshake completed50 ms
16 days agoHandshake completed42 ms
18 days agoHandshake completed45 ms
19 days agoHandshake completed52 ms
20 days agoHandshake completed60 ms
20 days agoHandshake completed49 ms
21 days agoHandshake completed44 ms
22 days agoHandshake completed80 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 GraphOS MCP Server and makes no claim about it beyond what these checks measured.