Is MCP down?
Down
Yes, MCP is down.
It has failed every check since 13 Oct 2026, 01:28 UTC (5 days 8 h, 6 checks). Latest error: initialize returned HTTP 503. It last passed on 12 Oct 2026, 16:30 UTC.
Latest check
- Last check
- 27 h ago (17 Oct 2026, 06:50 UTC)
- Response time
- Not measured (typical 611 ms)
- Next check
- Due now
- How often
- About every 10 hours over the last 7 days
Uptime
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
1 outage, 5 days 8 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 13 Oct 2026, 01:28 UTC | Ongoing, 5 days 8 h so far | 6 | initialize returned HTTP 503 |
Times are when our checks ran, about every 10 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 17 Oct 2026, 06:50 UTC | initialize returned HTTP 503 | 503 | 250 ms |
| 16 Oct 2026, 04:50 UTC | initialize returned HTTP 503 | 503 | 685 ms |
| 14 Oct 2026, 22:53 UTC | initialize returned HTTP 503 | 503 | 512 ms |
| 13 Oct 2026, 20:29 UTC | initialize returned HTTP 503 | 503 | 606 ms |
| 13 Oct 2026, 10:20 UTC | initialize returned HTTP 503 | 503 | 568 ms |
| 13 Oct 2026, 01:28 UTC | initialize returned HTTP 503 | 503 | 360 ms |
| 12 Oct 2026, 16:30 UTC | Passed | 401 | 611 ms |
| 12 Oct 2026, 06:38 UTC | Passed | 401 | 599 ms |
| 11 Oct 2026, 20:17 UTC | Passed | 401 | 901 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.