Is HTTP 431 header-fields-too-large down?

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

No, HTTP 431 header-fields-too-large is up.

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

Latest check

Last check: 10 h ago (17 Oct 2026, 20:14 UTC)
Response time: 203 ms (typical 69 ms)
Next check: Due now
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, 20:14 UTC	Passed	200	203 ms
17 Oct 2026, 09:13 UTC	Passed	200	331 ms
16 Oct 2026, 23:11 UTC	Passed	200	273 ms
16 Oct 2026, 12:55 UTC	Passed	200	69 ms
16 Oct 2026, 02:14 UTC	Passed	200	52 ms
15 Oct 2026, 16:35 UTC	Passed	200	53 ms
15 Oct 2026, 06:22 UTC	Passed	200	50 ms
14 Oct 2026, 20:25 UTC	Passed	200	165 ms
14 Oct 2026, 10:40 UTC	Passed	200	333 ms
14 Oct 2026, 00:48 UTC	Passed	200	408 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.