Is MCP Server down?
Down
Yes, MCP Server is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize returned HTTP 302.
Latest check
- Last check
- 47 h ago (9 Nov 2026, 08:47 UTC)
- Response time
- Not measured
- Next check
- In about 26 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, 08:47 UTC | initialize returned HTTP 302 | 302 | 373 ms |
| 6 Nov 2026, 11:09 UTC | initialize returned HTTP 302 | 302 | 428 ms |
| 3 Nov 2026, 03:13 UTC | initialize returned HTTP 302 | 302 | 458 ms |
| 30 Oct 2026, 19:09 UTC | initialize returned HTTP 302 | 302 | 433 ms |
| 27 Oct 2026, 11:14 UTC | initialize returned HTTP 302 | 302 | 397 ms |
| 23 Oct 2026, 22:20 UTC | initialize returned HTTP 302 | 302 | 433 ms |
| 20 Oct 2026, 20:40 UTC | initialize returned HTTP 302 | 302 | 511 ms |
| 19 Oct 2026, 18:37 UTC | initialize returned HTTP 302 | 302 | 493 ms |
| 18 Oct 2026, 15:37 UTC | initialize returned HTTP 302 | 302 | 465 ms |
| 17 Oct 2026, 09:11 UTC | initialize returned HTTP 302 | 302 | 424 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.