Registry Lag — how fast MCP directories reflect a new server

app.rowb.registry-lag/reflection · v1.0.0 · other

Registry Lag — how fast MCP directories reflect a new server is healthy: it completed an MCP handshake in 415 ms and exposes 2 tools. It scores 66/100.

Checks whether an MCP server is listed in MCP directories right now, and how long the listing took.

Endpoint: https://registry-lag.rowb.app/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Score 66/100

health	24.3 / 25
authEase	15 / 15
toolQuality	15 / 15
maintenance	7 / 15
adoption	0 / 10
usage	0 / 10
security	5 / 10

Scoring v0.3, computed 2026-10-14T20:21:39.733Z.

GitHub signals are off for everyone: maintenance uses registry dates (half credit)
No source repository listed

Health history

Checked (UTC)	Status	Latency	Error
2026-10-14T16:50:34.257Z	Healthy	415

Tools (2)

`check_directory_lag`	Check whether an MCP server name is listed in public MCP directories right now, and how long until it appeared (reflection lag).
`get_report`	Names checked so far with run counts and first/last seen timestamps.