Is FieldPulse MCP by usefulapi down?
Down
Yes, FieldPulse MCP by usefulapi is down.
It has not passed a check since we started checking it on 23 Oct 2026. Latest error: initialize returned HTTP 302.
Latest check
- Last check
- 47 h ago (9 Nov 2026, 04:15 UTC)
- Response time
- Not measured
- Next check
- In about 32 h
- 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 |
|---|---|---|---|
| 9 Nov 2026, 04:15 UTC | initialize returned HTTP 302 | 302 | 92 ms |
| 5 Nov 2026, 20:59 UTC | initialize returned HTTP 302 | 302 | 88 ms |
| 2 Nov 2026, 08:54 UTC | initialize returned HTTP 302 | 302 | 133 ms |
| 1 Nov 2026, 02:46 UTC | initialize returned HTTP 302 | 302 | 114 ms |
| 30 Oct 2026, 18:36 UTC | initialize returned HTTP 302 | 302 | 111 ms |
| 29 Oct 2026, 13:33 UTC | initialize returned HTTP 302 | 302 | 122 ms |
| 28 Oct 2026, 04:01 UTC | initialize returned HTTP 302 | 302 | 126 ms |
| 26 Oct 2026, 19:19 UTC | initialize returned HTTP 302 | 302 | 133 ms |
| 25 Oct 2026, 14:33 UTC | initialize returned HTTP 302 | 302 | 105 ms |
| 24 Oct 2026, 10:16 UTC | initialize returned HTTP 302 | 302 | 109 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.