Is mcpweave down?
Up
No, mcpweave is up.
It passed its latest check 5 h ago in 428 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 5 h ago (16 Oct 2026, 09:02 UTC)
- Response time
- 428 ms (typical 432 ms)
- Next check
- In about 4 h
- How often
- About every 9 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 9 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, 09:02 UTC | Passed | 401 | 428 ms |
| 15 Oct 2026, 23:05 UTC | Passed | 401 | 421 ms |
| 15 Oct 2026, 12:57 UTC | Passed | 401 | 476 ms |
| 15 Oct 2026, 03:37 UTC | Passed | 401 | 429 ms |
| 14 Oct 2026, 17:30 UTC | Passed | 401 | 434 ms |
| 14 Oct 2026, 07:34 UTC | Passed | 401 | 432 ms |
| 13 Oct 2026, 22:35 UTC | Passed | 401 | 424 ms |
| 13 Oct 2026, 13:05 UTC | Passed | 401 | 416 ms |
| 13 Oct 2026, 04:45 UTC | Passed | 401 | 426 ms |
| 12 Oct 2026, 20:05 UTC | Passed | 401 | 542 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 9 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.