Is Mail Blaze MCP by usefulapi down?
Down
Yes, Mail Blaze MCP by usefulapi is down.
It has not passed a check since we started checking it on 25 Oct 2026. Latest error: initialize returned HTTP 302.
Latest check
- Last check
- 8 h ago (10 Nov 2026, 20:18 UTC)
- Response time
- Not measured
- Next check
- In about 3 days
- How often
- About every 3 days over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 3 days 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, 20:18 UTC | initialize returned HTTP 302 | 302 | 92 ms |
| 7 Nov 2026, 11:59 UTC | initialize returned HTTP 302 | 302 | 140 ms |
| 4 Nov 2026, 06:15 UTC | initialize returned HTTP 302 | 302 | 123 ms |
| 2 Nov 2026, 22:49 UTC | initialize returned HTTP 302 | 302 | 200 ms |
| 1 Nov 2026, 17:04 UTC | initialize returned HTTP 302 | 302 | 73 ms |
| 31 Oct 2026, 12:15 UTC | initialize returned HTTP 302 | 302 | 91 ms |
| 30 Oct 2026, 06:21 UTC | initialize returned HTTP 302 | 302 | 156 ms |
| 28 Oct 2026, 22:41 UTC | initialize returned HTTP 302 | 302 | 180 ms |
| 27 Oct 2026, 15:12 UTC | initialize returned HTTP 302 | 302 | 127 ms |
| 26 Oct 2026, 08:38 UTC | initialize returned HTTP 302 | 302 | 115 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 3 days 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.