Is Registry Lag — how fast MCP directories reflect a new server down?

MCP serverBy registry-lag.rowb.app. How to connect and its trust score are on the listing page.

No, Registry Lag — how fast MCP directories reflect a new server is up.

It passed its latest check 7 h ago in 649 ms, and every check since we started checking it on 11 Oct 2026.

Latest check

Last check: 7 h ago (20 Oct 2026, 20:17 UTC)
Response time: 649 ms (typical 656 ms)
Next check: In about 3 h
How often: About every 10 hours over the last 7 days

Uptime

Last 24 hours100%2 checks

Last 7 days100%17 checks

Last 30 days100%24 checks

All checks passedSome failedAll failedNot checked

Uptime is the share of checks that passed. We checked it about every 10 hours over the last 7 days.

Outages in the last 30 days

No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.

Recent checks

When	Result	HTTP	Time
20 Oct 2026, 20:17 UTC	Passed	200	649 ms
20 Oct 2026, 10:45 UTC	Passed	200	667 ms
20 Oct 2026, 01:35 UTC	Passed	200	652 ms
19 Oct 2026, 16:09 UTC	Passed	200	659 ms
19 Oct 2026, 07:37 UTC	Passed	200	644 ms
18 Oct 2026, 22:27 UTC	Passed	200	657 ms
18 Oct 2026, 11:52 UTC	Passed	200	762 ms
18 Oct 2026, 01:45 UTC	Passed	200	592 ms
17 Oct 2026, 15:32 UTC	Passed	200	690 ms
17 Oct 2026, 04:33 UTC	Passed	200	656 ms

How we check

Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.

Checks come from our server, about every 10 hours for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.

If you think a check is wrong, contact hello@toolvet.app. More on how we check and score.