Is My MCP Server down?
Down
Yes, My MCP Server is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"}.
Latest check
- Last check
- 2 days ago (26 Oct 2026, 21:18 UTC)
- Response time
- Not measured
- Next check
- In about 23 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 |
|---|---|---|---|
| 26 Oct 2026, 21:18 UTC | initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"} | 200 | 584 ms |
| 23 Oct 2026, 15:00 UTC | initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"} | 200 | 546 ms |
| 20 Oct 2026, 12:02 UTC | initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"} | 200 | 592 ms |
| 19 Oct 2026, 07:11 UTC | initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"} | 200 | 556 ms |
| 18 Oct 2026, 04:28 UTC | initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"} | 200 | 739 ms |
| 17 Oct 2026, 01:59 UTC | initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"} | 200 | 579 ms |
| 15 Oct 2026, 23:52 UTC | initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"} | 200 | 541 ms |
| 14 Oct 2026, 22:06 UTC | initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"} | 200 | 554 ms |
| 13 Oct 2026, 20:33 UTC | initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"} | 200 | 566 ms |
| 12 Oct 2026, 16:18 UTC | initialize failed: {"code":-32603,"message":"MCP error -32603: Internal Server Error"} | 200 | 507 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.