app.rowb.registry-lag/reflection
Registry Lag — how fast MCP directories reflect a new server
Checks whether an MCP server is listed in MCP directories right now, and how long the listing took.
timeout probed 2026-10-15
fetch failed | Connect Timeout Error (attempted address: registry-lag.rowb.app:443, timeout: 10000ms) | UND_ERR_CONNECT_TIMEOUT
- Endpoint
- https://registry-lag.rowb.app/mcp (streamable-http)
- Host
- registry-lag.rowb.app
- Website
- https://registry-lag.rowb.app
- Registry
- active, updated 2026-09-26 · registry entry
- Reachable
- 6 of the last 6 probes
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-05 12:42 | alive | 578 ms | 2 | 184 | 103 |
| 2026-10-05 00:08 | alive | 461 ms | 2 | 103 | |
| 2026-10-04 09:53 | alive | 734 ms | 2 | 103 | |
| 2026-10-04 07:47 | alive | 835 ms | 2 | 103 | |
| 2026-10-03 20:27 | alive | 665 ms | 2 | 103 | |
| 2026-10-03 17:46 | alive | 733 ms | 2 | 103 |
Badge and feed
[](https://mcpcost.ulehla.dev/s/app.rowb.registry-lag/reflection)
An entry for every probe that changed the result, the tool count or the token cost: Atom feed. Add it to a feed reader or a Slack RSS app to hear when the server stops answering or its tool set grows.