Remote MCP · Endpoint
Registry Lag — how fast MCP directories reflect a new server MCP server
No. Registry Lag — how fast MCP directories reflect a new server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://registry-lag.rowb.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.rowb.registry-lag/reflection
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 474 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 15 checks
- Described by its publisher as
- Checks whether an MCP server is listed in MCP directories right now, and how long the listing took.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 474 ms |
| 2 days ago | Handshake completed | 408 ms |
| 4 days ago | Handshake completed | 520 ms |
| 6 days ago | Handshake completed | 439 ms |
| 8 days ago | Handshake completed | 465 ms |
| 9 days ago | Handshake completed | 464 ms |
| 11 days ago | Handshake completed | 537 ms |
| 12 days ago | Handshake completed | 821 ms |
| 13 days ago | Handshake completed | 401 ms |
| 16 days ago | Handshake completed | 397 ms |
| 17 days ago | Handshake completed | 419 ms |
| 19 days ago | Handshake completed | 460 ms |
| 21 days ago | Handshake completed | 406 ms |
| 22 days ago | Handshake completed | 438 ms |
| 23 days ago | Handshake completed | 442 ms |
The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.
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 Lag — how fast MCP directories reflect a new server and makes no claim about it beyond what these checks measured.