Remote MCP · Endpoint

Registry Rot Watch MCP server

No. Registry Rot Watch answered an MCP handshake 38 minutes ago.

UpLast checked 38 minutes ago

Server URL

https://textforagents.com/products/registry-rot-watch/mcp

The last check completed an MCP handshake.

Registry name
com.textforagents/registry-rot-watch
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
16 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Registry Rot Watch: liveness + successor-contract verdicts for MCP endpoints.
Listing
From the official MCP registry (active).
Recent checks of Registry Rot Watch
CheckedResultHandshake
38 minutes agoHandshake completed16 ms
3 days agoHandshake completed1.31 s
12 days agoHandshake completed54 ms
12 days agoHandshake completed69 ms
14 days agoHandshake completed66 ms
15 days agoHandshake completed41 ms
16 days agoHandshake completed44 ms
17 days agoHandshake completed158 ms
18 days agoHandshake completed17 ms
19 days agoHandshake completed45 ms
22 days agoHandshake completed16 ms
25 days agoHandshake completed15 ms
27 days agoHandshake completed17 ms

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

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 Registry Rot Watch and makes no claim about it beyond what these checks measured.