Is ShotAPI MCP Server down?
Up
No, ShotAPI MCP Server is up.
It passed its latest check 9 h ago in 894 ms. It has passed every check since 16 Oct 2026, 03:17 UTC.
Latest check
- Last check
- 9 h ago (16 Oct 2026, 03:17 UTC)
- Response time
- 894 ms (typical 894 ms)
- Next check
- Due now
- How often
- About every 28 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 28 hours 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 |
|---|---|---|---|
| 16 Oct 2026, 03:17 UTC | Passed | 401 | 894 ms |
| 14 Oct 2026, 22:36 UTC | Connection failed: Response does not match the HTTP/1.1 protocol (Missing expected CR after response line) | - | - |
| 13 Oct 2026, 18:11 UTC | Connection failed: Response does not match the HTTP/1.1 protocol (Missing expected CR after response line) | - | - |
| 12 Oct 2026, 14:31 UTC | Connection failed: Response does not match the HTTP/1.1 protocol (Missing expected CR after response line) | - | - |
| 12 Oct 2026, 04:47 UTC | Connection failed: Response does not match the HTTP/1.1 protocol (Missing expected CR after response line) | - | - |
| 11 Oct 2026, 19:02 UTC | Connection failed: Response does not match the HTTP/1.1 protocol (Missing expected CR after response line) | - | - |
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 28 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.