← Back to the index
Registry updated within 120 days · Remote · publisher endpoint

Registry Lag — how fast MCP directories reflect a new server NEW

app.rowb.registry-lag/reflection copy

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

CategoryOther
TransportRemote
Registry freshnessRegistry updated within 120 days
Version1.0.0
Distributionhosted
Maintainerregistry-lag

Install & connect

Connect · publisher endpointremote
https://registry-lag.rowb.app/mcp

Publisher-declared remote endpoint. Availability, authentication and client compatibility are not independently verified here.

Freshness

Maintained · updated this quarter

Last registry update 1mo ago · published Sep 26, 2026.

Registry position over time

Where Registry Lag — how fast MCP directories reflect a new server sits in the freshest-first index, tracked daily — new to the tracked index since the prior run. position movement fills in as the index runs daily.

Current position#29986
Best position#29986
Since prior runNEW

About this server

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

Hosted — runs on the provider's infrastructure; connect over HTTP/SSE. Indexed under Other, alongside 8606 other servers. Health is freshness-derived from the registry's last-update timestamp; this index does not run the server, so capabilities and tool lists live in the source repository.

More in Other 8607

Browse all 8606 in Other →
Published · Sep 26, 2026
Updated · Sep 26, 2026
Source · official Model Context Protocol registry