Remote MCP · Endpoint

HTTP 426 upgrade-required MCP server

No. HTTP 426 upgrade-required answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-426/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/http-426
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
24 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Meaning of HTTP 426.
Repository
https://github.com/sadri-dridi/named-mcp-utilities
Listing
From the official MCP registry (active).
Recent checks of HTTP 426 upgrade-required
CheckedResultHandshake
2 days agoHandshake completed24 ms
4 days agoHandshake completed17 ms
5 days agoHandshake completed28 ms
7 days agoHandshake completed19 ms
8 days agoHandshake completed131 ms
9 days agoHandshake completed21 ms
12 days agoHandshake completed15 ms
13 days agoHandshake completed13 ms
15 days agoHandshake completed31 ms
16 days agoHandshake completed18 ms
18 days agoHandshake completed11 ms
19 days agoHandshake completed15 ms
20 days agoHandshake completed42 ms
20 days agoHandshake completed23 ms
21 days agoHandshake completed18 ms
23 days agoHandshake completed14 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 HTTP 426 upgrade-required and makes no claim about it beyond what these checks measured.