Is 16 random hex chars down?

MCP serverBy agent-observatory-sensor.nolimit-observatory.workers.dev. How to connect and its trust score are on the listing page.

No, 16 random hex chars is up.

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

Latest check

Last check: 8 h ago (18 Oct 2026, 12:37 UTC)
Response time: 164 ms (typical 297 ms)
Next check: In about 2 h
How often: About every 10 hours over the last 7 days

Uptime

Last 24 hours100%2 checks

Last 7 days100%16 checks

Last 30 days100%17 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
18 Oct 2026, 12:37 UTC	Passed	200	164 ms
18 Oct 2026, 02:17 UTC	Passed	200	144 ms
17 Oct 2026, 15:45 UTC	Passed	200	2.7 s
17 Oct 2026, 04:34 UTC	Passed	200	347 ms
16 Oct 2026, 18:03 UTC	Passed	200	617 ms
16 Oct 2026, 07:32 UTC	Passed	200	341 ms
15 Oct 2026, 21:18 UTC	Passed	200	297 ms
15 Oct 2026, 11:30 UTC	Passed	200	45 ms
15 Oct 2026, 01:09 UTC	Passed	200	67 ms
14 Oct 2026, 15:13 UTC	Passed	200	80 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.