Remote MCP · Endpoint

MCP Registry Validator — Check Endpoints Actually Resolve MCP server

Yes, as of 2 hours ago: the server returned an HTTP error.

DownLast checked 2 hours ago

Server URL

https://mcp-uptime.theopslog.workers.dev/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.operatorsheets/mcp-uptime
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
4 tools
Uptime, last 30 days
88.2% from 17 checks
Described by its publisher as
Check an MCP endpoint resolves: liveness, live tool list, schema drift. Free.
Listing
From the official MCP registry (deprecated).
Recent checks of MCP Registry Validator — Check Endpoints Actually Resolve
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoHandshake completed240 ms
5 days agoHandshake completed90 ms
7 days agoHandshake completed286 ms
8 days agoHandshake completed419 ms
9 days agoHandshake completed90 ms
12 days agoHandshake completed99 ms
13 days agoHandshake completed134 ms
15 days agoHandshake completed102 ms
17 days agoHandshake completed235 ms
18 days agoHandshake completed206 ms
19 days agoHandshake completed153 ms
20 days agoHandshake completed99 ms
20 days agoHandshake completed222 ms
21 days agoHandshake completed218 ms
23 days agoHandshake completed206 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 15 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.

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 MCP Registry Validator — Check Endpoints Actually Resolve and makes no claim about it beyond what these checks measured.