Is Bouncify MCP by usefulapi down?
Down
Yes, Bouncify MCP by usefulapi is down.
It has not passed a check since we started checking it on 29 Oct 2026. Latest error: initialize returned HTTP 302.
Latest check
- Last check
- 2 days ago (8 Nov 2026, 23:22 UTC)
- Response time
- Not measured
- Next check
- In about 23 h
- 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 |
|---|---|---|---|
| 8 Nov 2026, 23:22 UTC | initialize returned HTTP 302 | 302 | 77 ms |
| 7 Nov 2026, 17:46 UTC | initialize returned HTTP 302 | 302 | 89 ms |
| 6 Nov 2026, 09:58 UTC | initialize returned HTTP 302 | 302 | 128 ms |
| 5 Nov 2026, 03:51 UTC | initialize returned HTTP 302 | 302 | 85 ms |
| 3 Nov 2026, 17:44 UTC | initialize returned HTTP 302 | 302 | 153 ms |
| 2 Nov 2026, 10:14 UTC | initialize returned HTTP 302 | 302 | 113 ms |
| 1 Nov 2026, 07:33 UTC | initialize returned HTTP 302 | 302 | 108 ms |
| 31 Oct 2026, 00:08 UTC | initialize returned HTTP 302 | 302 | 73 ms |
| 30 Oct 2026, 10:40 UTC | initialize returned HTTP 302 | 302 | 119 ms |
| 29 Oct 2026, 20:49 UTC | initialize returned HTTP 302 | 302 | 344 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 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.