Remote MCP · Endpoint

HTTP 502 bad-gateway MCP server

No. HTTP 502 bad-gateway answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/http-502
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
28 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Meaning of HTTP 502.
Repository
https://github.com/sadri-dridi/named-mcp-utilities
Listing
From the official MCP registry (active).
Recent checks of HTTP 502 bad-gateway
CheckedResultHandshake
2 hours agoHandshake completed28 ms
1 day agoHandshake completed17 ms
2 days agoHandshake completed22 ms
3 days agoHandshake completed22 ms
4 days agoHandshake completed24 ms
5 days agoHandshake completed279 ms
7 days agoHandshake completed16 ms
9 days agoHandshake completed31 ms
11 days agoHandshake completed18 ms
14 days agoHandshake completed24 ms
16 days agoHandshake completed45 ms
18 days agoHandshake completed22 ms
20 days agoHandshake completed20 ms
22 days agoHandshake completed12 ms
24 days agoHandshake completed15 ms
26 days agoHandshake completed14 ms
27 days agoHandshake completed21 ms
29 days agoHandshake completed24 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

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 502 bad-gateway and makes no claim about it beyond what these checks measured.