MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

Publisher portfolio

registry-lag.rowb.app

Explore the MCP servers published by registry-lag.rowb.app, with independent connection checks, performance measurements, and setup instructions for each project.

Listed servers
1

Active projects in this portfolio. Deleted and deprecated registry rows are excluded.

Sampled servers
0

Active servers with a recorded connection probe

Latest probe connected
0

Latest stored probe connected. This is not a live guarantee.

Repositories
0

Distinct source repositories linked by the active listings

Portfolio overview

MCP servers

Compare connection status and measurements. Open a server for its tools, check results, and client configuration.

Dated server measurements. The status describes the last probe or a listed authentication requirement. Checks that have not been measured are not failures. Open a server to inspect the evidence.
Server / capabilityLast probeMedian latencyChecks passedLast checked
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.

Developer ToolsCode & DevOps

Requires authNot measured4 / 22Not checked yet

Company & identity

About registry-lag.rowb.app

registry-lag.rowb.app publishes MCP servers under the app.rowb.registry-lag namespace. This namespace uses a reverse-domain identity in the directory.

Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.

Source repositories

No source repositories listed yet.