Remote MCP · Endpoint

dev.pages.proofrun/proofrun MCP server

No. dev.pages.proofrun/proofrun answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://proofrun.pages.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.pages.proofrun/proofrun
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
682 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
ProofRun: bounded HTTP acceptance checks for agent deployments. $0.01 USDC per pack.
Website
https://proofrun.pages.dev/
Listing
From the official MCP registry (active).
Recent checks of dev.pages.proofrun/proofrun
CheckedResultHandshake
1 hour agoHandshake completed682 ms
11 hours agoHandshake completed875 ms
1 day agoHandshake completed1.39 s
2 days agoHandshake completed800 ms
4 days agoHandshake completed500 ms
4 days agoHandshake completed522 ms
5 days agoHandshake completed524 ms
6 days agoHandshake completed488 ms
8 days agoHandshake completed840 ms
11 days agoHandshake completed865 ms
13 days agoHandshake completed1.23 s
16 days agoHandshake completed391 ms
18 days agoHandshake completed707 ms
20 days agoHandshake completed1.05 s
22 days agoHandshake completed444 ms
24 days agoHandshake completed271 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with dev.pages.proofrun/proofrun and makes no claim about it beyond what these checks measured.