Is Freshly Inventory MCP by usefulapi down?
Down
Yes, Freshly Inventory MCP by usefulapi is down.
It has not passed a check since we started checking it on 1 Nov 2026. Latest error: initialize returned HTTP 302.
Latest check
- Last check
- 22 h ago (10 Nov 2026, 07:09 UTC)
- Response time
- Not measured
- Next check
- In about 8 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 |
|---|---|---|---|
| 10 Nov 2026, 07:09 UTC | initialize returned HTTP 302 | 302 | 144 ms |
| 9 Nov 2026, 00:06 UTC | initialize returned HTTP 302 | 302 | 73 ms |
| 7 Nov 2026, 18:33 UTC | initialize returned HTTP 302 | 302 | 117 ms |
| 6 Nov 2026, 12:30 UTC | initialize returned HTTP 302 | 302 | 78 ms |
| 5 Nov 2026, 05:26 UTC | initialize returned HTTP 302 | 302 | 149 ms |
| 3 Nov 2026, 22:26 UTC | initialize returned HTTP 302 | 302 | 75 ms |
| 2 Nov 2026, 16:22 UTC | initialize returned HTTP 302 | 302 | 107 ms |
| 2 Nov 2026, 03:23 UTC | initialize returned HTTP 302 | 302 | 110 ms |
| 1 Nov 2026, 17:31 UTC | initialize returned HTTP 302 | 302 | 475 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.