Is CRC-64 hex length, input discarded down?

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

No, CRC-64 hex length, input discarded is up.

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

Latest check

Last check: 9 h ago (17 Oct 2026, 12:56 UTC)
Response time: 315 ms (typical 58 ms)
Next check: In about 64 min
How often: About every 10 hours over the last 7 days

Uptime

Last 24 hours100%2 checks

Last 7 days100%15 checks

Last 30 days100%15 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
17 Oct 2026, 12:56 UTC	Passed	200	315 ms
17 Oct 2026, 02:32 UTC	Passed	200	54 ms
16 Oct 2026, 16:27 UTC	Passed	200	58 ms
16 Oct 2026, 05:40 UTC	Passed	200	62 ms
15 Oct 2026, 19:46 UTC	Passed	200	398 ms
15 Oct 2026, 09:51 UTC	Passed	200	40 ms
15 Oct 2026, 00:27 UTC	Passed	200	64 ms
14 Oct 2026, 14:45 UTC	Passed	200	39 ms
14 Oct 2026, 05:02 UTC	Passed	200	49 ms
13 Oct 2026, 20:08 UTC	Passed	200	68 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.