Is Workyard MCP by usefulapi down?
Down
Yes, Workyard MCP by usefulapi is down.
It has not passed a check since we started checking it on 28 Oct 2026. Latest error: initialize returned HTTP 302.
Latest check
- Last check
- 3 h ago (11 Nov 2026, 01:43 UTC)
- Response time
- Not measured
- Next check
- In about 3 days
- 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 |
|---|---|---|---|
| 11 Nov 2026, 01:43 UTC | initialize returned HTTP 302 | 302 | 81 ms |
| 7 Nov 2026, 21:48 UTC | initialize returned HTTP 302 | 302 | 101 ms |
| 6 Nov 2026, 14:24 UTC | initialize returned HTTP 302 | 302 | 136 ms |
| 5 Nov 2026, 09:54 UTC | initialize returned HTTP 302 | 302 | 136 ms |
| 4 Nov 2026, 01:08 UTC | initialize returned HTTP 302 | 302 | 101 ms |
| 2 Nov 2026, 18:00 UTC | initialize returned HTTP 302 | 302 | 108 ms |
| 1 Nov 2026, 09:26 UTC | initialize returned HTTP 302 | 302 | 70 ms |
| 31 Oct 2026, 02:16 UTC | initialize returned HTTP 302 | 302 | 79 ms |
| 29 Oct 2026, 20:59 UTC | initialize returned HTTP 302 | 302 | 113 ms |
| 29 Oct 2026, 07:04 UTC | initialize returned HTTP 302 | 302 | 120 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.