Remote MCP · Endpoint

RFC errata id shape, value discarded MCP server

No. RFC errata id shape, value discarded answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/rfc-errata-ok/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/rfc-errata-ok
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
17 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
RFC errata id shape, value discarded
Listing
From the official MCP registry (active).
Recent checks of RFC errata id shape, value discarded
CheckedResultHandshake
2 days agoHandshake completed17 ms
3 days agoHandshake completed37 ms
3 days agoHandshake completed23 ms
5 days agoHandshake completed18 ms
6 days agoHandshake completed24 ms
7 days agoHandshake completed21 ms
8 days agoHandshake completed18 ms
9 days agoHandshake completed22 ms
11 days agoHandshake completed19 ms
14 days agoHandshake completed331 ms
16 days agoHandshake completed23 ms
19 days agoHandshake completed23 ms
21 days agoHandshake completed14 ms
23 days agoHandshake completed23 ms
25 days agoHandshake completed19 ms
27 days agoHandshake completed19 ms
29 days agoHandshake completed15 ms
30 days agoHandshake completed18 ms
32 days agoHandshake completed21 ms

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

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 RFC errata id shape, value discarded and makes no claim about it beyond what these checks measured.