Is Adler-32 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, Adler-32 hex length, input discarded is up.

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

Latest check

Last check: 8 h ago (17 Oct 2026, 00:55 UTC)
Response time: 53 ms (typical 41 ms)
Next check: In about 89 min
How often: About every 10 hours over the last 7 days

Uptime

Last 24 hours100%2 checks

Last 7 days100%14 checks

Last 30 days100%14 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, 00:55 UTC	Passed	200	53 ms
16 Oct 2026, 15:06 UTC	Passed	200	51 ms
16 Oct 2026, 04:25 UTC	Passed	200	36 ms
15 Oct 2026, 18:18 UTC	Passed	200	112 ms
15 Oct 2026, 08:23 UTC	Passed	200	54 ms
14 Oct 2026, 22:22 UTC	Passed	200	37 ms
14 Oct 2026, 13:06 UTC	Passed	200	93 ms
14 Oct 2026, 03:53 UTC	Passed	200	35 ms
13 Oct 2026, 18:37 UTC	Passed	200	57 ms
13 Oct 2026, 09:21 UTC	Passed	200	41 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.