Remote MCP · Endpoint

Graph Paper MCP server

No. Graph Paper answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://graph-paper.io/mcp

The last check completed an MCP handshake.

Registry name
io.graph-paper/graph-paper
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
106 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check a plot document and get a link that opens it in Graph Paper. No account, no key.
Listing
From the official MCP registry (active).
Recent checks of Graph Paper
CheckedResultHandshake
1 hour agoHandshake completed106 ms
2 days agoHandshake completed248 ms
4 days agoHandshake completed417 ms
7 days agoHandshake completed104 ms
9 days agoHandshake completed98 ms
11 days agoHandshake completed104 ms
13 days agoHandshake completed152 ms
15 days agoHandshake completed67 ms
16 days agoHandshake completed149 ms
18 days agoHandshake completed78 ms
19 days agoHandshake completed383 ms
20 days agoHandshake completed171 ms
23 days agoHandshake completed79 ms
24 days agoHandshake completed164 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 Graph Paper and makes no claim about it beyond what these checks measured.