Is Fitssey MCP by usefulapi down?
Down
Yes, Fitssey 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
- 32 h ago (9 Nov 2026, 20:44 UTC)
- Response time
- Not measured
- Next check
- In about 40 h
- How often
- About every 31 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 31 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, 20:44 UTC | initialize returned HTTP 302 | 302 | 115 ms |
| 8 Nov 2026, 14:47 UTC | initialize returned HTTP 302 | 302 | 77 ms |
| 7 Nov 2026, 11:03 UTC | initialize returned HTTP 302 | 302 | 116 ms |
| 6 Nov 2026, 02:34 UTC | initialize returned HTTP 302 | 302 | 68 ms |
| 4 Nov 2026, 15:19 UTC | initialize returned HTTP 302 | 302 | 83 ms |
| 3 Nov 2026, 06:52 UTC | initialize returned HTTP 302 | 302 | 86 ms |
| 1 Nov 2026, 20:16 UTC | initialize returned HTTP 302 | 302 | 119 ms |
| 31 Oct 2026, 18:23 UTC | initialize returned HTTP 302 | 302 | 108 ms |
| 31 Oct 2026, 05:01 UTC | initialize returned HTTP 302 | 302 | 116 ms |
| 30 Oct 2026, 15:30 UTC | initialize returned HTTP 302 | 302 | 168 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 31 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.