Is Covenant AAP - hosted developer pilot down?
Up
No, Covenant AAP - hosted developer pilot is up.
It passed its latest check 6 h ago in 441 ms. It has passed every check since 10 Nov 2026, 10:51 UTC.
Latest check
- Last check
- 6 h ago (10 Nov 2026, 10:51 UTC)
- Response time
- 441 ms (typical 441 ms)
- Next check
- Not before 10 Nov 2026, 17:02 UTC
- How often
- About every 30 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 30 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 |
|---|---|---|---|
| 10 Nov 2026, 10:51 UTC | Passed | 200 | 441 ms |
| 9 Nov 2026, 06:27 UTC | initialize failed: {"code":-32602,"data":{"code":"MCP_CONNECTED_PROTOCOL","fix":"This versioned preview profile uses MCP 2025-11-25. Send that protocol version, a capabilities object and clientInfo with bounded name and | 200 | 1.2 s |
| 8 Nov 2026, 01:34 UTC | initialize failed: {"code":-32602,"data":{"code":"MCP_CONNECTED_PROTOCOL","fix":"This versioned preview profile uses MCP 2025-11-25. Send that protocol version, a capabilities object and clientInfo with bounded name and | 200 | 782 ms |
| 6 Nov 2026, 19:43 UTC | initialize failed: {"code":-32602,"data":{"code":"MCP_CONNECTED_PROTOCOL","fix":"This versioned preview profile uses MCP 2025-11-25. Send that protocol version, a capabilities object and clientInfo with bounded name and | 200 | 1.2 s |
| 5 Nov 2026, 12:44 UTC | initialize failed: {"code":-32602,"data":{"code":"MCP_CONNECTED_PROTOCOL","fix":"This versioned preview profile uses MCP 2025-11-25. Send that protocol version, a capabilities object and clientInfo with bounded name and | 200 | 1.2 s |
| 4 Nov 2026, 04:11 UTC | initialize failed: {"code":-32602,"data":{"code":"MCP_CONNECTED_PROTOCOL","fix":"This versioned preview profile uses MCP 2025-11-25. Send that protocol version, a capabilities object and clientInfo with bounded name and | 200 | 1.0 s |
| 2 Nov 2026, 20:35 UTC | initialize failed: {"code":-32602,"data":{"code":"MCP_CONNECTED_PROTOCOL","fix":"This versioned preview profile uses MCP 2025-11-25. Send that protocol version, a capabilities object and clientInfo with bounded name and | 200 | 870 ms |
| 1 Nov 2026, 13:32 UTC | initialize failed: {"code":-32602,"data":{"code":"MCP_CONNECTED_PROTOCOL","fix":"This versioned preview profile uses MCP 2025-11-25. Send that protocol version, a capabilities object and clientInfo with bounded name and | 200 | 1.0 s |
| 1 Nov 2026, 00:01 UTC | initialize failed: {"code":-32602,"data":{"code":"MCP_CONNECTED_PROTOCOL","fix":"This versioned preview profile uses MCP 2025-11-25. Send that protocol version, a capabilities object and clientInfo with bounded name and | 200 | 760 ms |
| 31 Oct 2026, 10:13 UTC | initialize failed: {"code":-32602,"data":{"code":"MCP_CONNECTED_PROTOCOL","fix":"This versioned preview profile uses MCP 2025-11-25. Send that protocol version, a capabilities object and clientInfo with bounded name and | 200 | 1.1 s |
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 30 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.