Is MCP host-behaviour census down?
Up
No, MCP host-behaviour census is up.
It passed its latest check 10 h ago in 335 ms, and every check since we started checking it on 21 Oct 2026.
Latest check
- Last check
- 10 h ago (7 Nov 2026, 00:50 UTC)
- Response time
- 335 ms (typical 345 ms)
- Next check
- In about 4 h
- How often
- About every 14 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 14 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 |
|---|---|---|---|
| 7 Nov 2026, 00:50 UTC | Passed | 200 | 335 ms |
| 6 Nov 2026, 13:44 UTC | Passed | 200 | 342 ms |
| 6 Nov 2026, 01:35 UTC | Passed | 200 | 347 ms |
| 5 Nov 2026, 10:09 UTC | Passed | 200 | 340 ms |
| 4 Nov 2026, 18:44 UTC | Passed | 200 | 341 ms |
| 4 Nov 2026, 03:36 UTC | Passed | 200 | 341 ms |
| 3 Nov 2026, 13:36 UTC | Passed | 200 | 378 ms |
| 2 Nov 2026, 23:20 UTC | Passed | 200 | 115 ms |
| 2 Nov 2026, 10:01 UTC | Passed | 200 | 350 ms |
| 1 Nov 2026, 23:31 UTC | Passed | 200 | 126 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 14 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.