Is Kolada MCP Server down?
Down
Yes, Kolada MCP Server is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize returned HTTP 503.
Latest check
- Last check
- 32 h ago (26 Oct 2026, 23:58 UTC)
- Response time
- Not measured
- Next check
- In about 46 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, 23:58 UTC | initialize returned HTTP 503 | 503 | 89 ms |
| 23 Oct 2026, 22:56 UTC | initialize returned HTTP 503 | 503 | 102 ms |
| 20 Oct 2026, 18:05 UTC | initialize returned HTTP 503 | 503 | 183 ms |
| 19 Oct 2026, 14:19 UTC | initialize returned HTTP 503 | 503 | 188 ms |
| 18 Oct 2026, 10:42 UTC | initialize returned HTTP 503 | 503 | 217 ms |
| 17 Oct 2026, 06:26 UTC | initialize returned HTTP 503 | 503 | 146 ms |
| 16 Oct 2026, 04:21 UTC | initialize returned HTTP 503 | 503 | 196 ms |
| 14 Oct 2026, 23:58 UTC | initialize returned HTTP 503 | 503 | 175 ms |
| 13 Oct 2026, 19:10 UTC | initialize returned HTTP 503 | 503 | 151 ms |
| 12 Oct 2026, 14:29 UTC | initialize returned HTTP 503 | 503 | 90 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.