Is Collmex MCP by usefulapi down?
Down
Yes, Collmex MCP by usefulapi is down.
It has not passed a check since we started checking it on 30 Oct 2026. Latest error: initialize returned HTTP 302.
Latest check
- Last check
- 46 h ago (9 Nov 2026, 06:37 UTC)
- Response time
- Not measured
- Next check
- In about 33 h
- 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 |
|---|---|---|---|
| 9 Nov 2026, 06:37 UTC | initialize returned HTTP 302 | 302 | 81 ms |
| 8 Nov 2026, 02:13 UTC | initialize returned HTTP 302 | 302 | 76 ms |
| 6 Nov 2026, 23:15 UTC | initialize returned HTTP 302 | 302 | 83 ms |
| 5 Nov 2026, 19:08 UTC | initialize returned HTTP 302 | 302 | 106 ms |
| 4 Nov 2026, 11:33 UTC | initialize returned HTTP 302 | 302 | 102 ms |
| 3 Nov 2026, 01:27 UTC | initialize returned HTTP 302 | 302 | 141 ms |
| 1 Nov 2026, 15:39 UTC | initialize returned HTTP 302 | 302 | 105 ms |
| 31 Oct 2026, 12:49 UTC | initialize returned HTTP 302 | 302 | 233 ms |
| 30 Oct 2026, 23:16 UTC | initialize returned HTTP 302 | 302 | 91 ms |
| 30 Oct 2026, 09:15 UTC | initialize returned HTTP 302 | 302 | 354 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 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.