Is Validatethat MCP down?
Down
Yes, Validatethat MCP is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize returned HTTP 405.
Latest check
- Last check
- 35 h ago (9 Nov 2026, 06:36 UTC)
- Response time
- Not measured
- Next check
- In about 40 h
- How often
- About every 3 days over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 3 days 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 |
|---|---|---|---|
| 9 Nov 2026, 06:36 UTC | initialize returned HTTP 405 | 405 | 194 ms |
| 6 Nov 2026, 07:04 UTC | initialize returned HTTP 405 | 405 | 191 ms |
| 2 Nov 2026, 21:57 UTC | initialize returned HTTP 405 | 405 | 271 ms |
| 30 Oct 2026, 11:21 UTC | initialize returned HTTP 405 | 405 | 221 ms |
| 27 Oct 2026, 04:49 UTC | initialize returned HTTP 405 | 405 | 191 ms |
| 23 Oct 2026, 15:56 UTC | initialize returned HTTP 405 | 405 | 262 ms |
| 20 Oct 2026, 13:41 UTC | initialize returned HTTP 405 | 405 | 978 ms |
| 19 Oct 2026, 11:53 UTC | initialize returned HTTP 405 | 405 | 307 ms |
| 18 Oct 2026, 11:25 UTC | initialize returned HTTP 405 | 405 | 179 ms |
| 17 Oct 2026, 05:44 UTC | initialize returned HTTP 405 | 405 | 169 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 3 days 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.