Is HTTP 501 not-implemented down?

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

No, HTTP 501 not-implemented is up.

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

Latest check

Last check: 8 h ago (17 Oct 2026, 22:24 UTC)
Response time: 39 ms (typical 46 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%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

When	Result	HTTP	Time
17 Oct 2026, 22:24 UTC	Passed	200	39 ms
17 Oct 2026, 11:32 UTC	Passed	200	49 ms
17 Oct 2026, 00:49 UTC	Passed	200	37 ms
16 Oct 2026, 14:21 UTC	Passed	200	56 ms
16 Oct 2026, 04:26 UTC	Passed	200	282 ms
15 Oct 2026, 18:36 UTC	Passed	200	59 ms
15 Oct 2026, 08:31 UTC	Passed	200	66 ms
14 Oct 2026, 22:09 UTC	Passed	200	48 ms
14 Oct 2026, 12:30 UTC	Passed	200	65 ms
14 Oct 2026, 03:22 UTC	Passed	200	34 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.