Is djb2 hex, input discarded down?

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

Up

No, djb2 hex, input discarded is up.

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

Latest check

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

Uptime

Last 24 hours100%3 checks
Last 7 days100%16 checks
Last 30 days100%16 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

WhenResultHTTPTime
17 Oct 2026, 20:17 UTCPassed200307 ms
17 Oct 2026, 09:07 UTCPassed200565 ms
16 Oct 2026, 22:38 UTCPassed200311 ms
16 Oct 2026, 12:52 UTCPassed20047 ms
16 Oct 2026, 03:05 UTCPassed20045 ms
15 Oct 2026, 17:04 UTCPassed200367 ms
15 Oct 2026, 07:10 UTCPassed200454 ms
14 Oct 2026, 21:00 UTCPassed20052 ms
14 Oct 2026, 11:03 UTCPassed200399 ms
14 Oct 2026, 02:03 UTCPassed20039 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.