Is ClosedMCP down?
Up
No, ClosedMCP is up.
It passed its latest check 4 h ago in 590 ms. It has passed every check since 5 Nov 2026, 16:47 UTC.
Latest check
- Last check
- 4 h ago (8 Nov 2026, 04:46 UTC)
- Response time
- 590 ms (typical 450 ms)
- Next check
- In about 8 h
- How often
- About every 13 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 13 hours over the last 7 days.
Outages in the last 30 days
1 outage, 2 days 12 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 3 Nov 2026, 04:56 UTC | 2 days 12 h | 3 | Connection failed (ECONNREFUSED) |
Times are when our checks ran, about every 13 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 8 Nov 2026, 04:46 UTC | Passed | 401 | 590 ms |
| 7 Nov 2026, 18:08 UTC | Passed | 401 | 992 ms |
| 7 Nov 2026, 05:53 UTC | Passed | 401 | 442 ms |
| 6 Nov 2026, 18:47 UTC | Passed | 401 | 448 ms |
| 6 Nov 2026, 07:31 UTC | Passed | 401 | 484 ms |
| 5 Nov 2026, 16:47 UTC | Passed | 401 | 434 ms |
| 4 Nov 2026, 09:45 UTC | Connection failed (ECONNREFUSED) | - | - |
| 3 Nov 2026, 19:06 UTC | Connection failed (ECONNREFUSED) | - | - |
| 3 Nov 2026, 04:56 UTC | Connection failed (ECONNREFUSED) | - | - |
| 2 Nov 2026, 15:14 UTC | Passed | 401 | 472 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 13 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.