Is webforJ MCP Server down?
Up
No, webforJ MCP Server is up.
It passed its latest check 1 min ago in 275 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 1 min ago (20 Oct 2026, 12:46 UTC)
- Response time
- 275 ms (typical 161 ms)
- Next check
- In about 10 h
- How often
- About every 10 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 10 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 |
|---|---|---|---|
| 20 Oct 2026, 12:46 UTC | Passed | 200 | 275 ms |
| 20 Oct 2026, 03:04 UTC | Passed | 200 | 104 ms |
| 19 Oct 2026, 17:11 UTC | Passed | 200 | 150 ms |
| 19 Oct 2026, 08:11 UTC | Passed | 200 | 198 ms |
| 18 Oct 2026, 23:20 UTC | Passed | 200 | 159 ms |
| 18 Oct 2026, 13:19 UTC | Passed | 200 | 173 ms |
| 18 Oct 2026, 02:52 UTC | Passed | 200 | 133 ms |
| 17 Oct 2026, 15:37 UTC | Passed | 200 | 98 ms |
| 17 Oct 2026, 04:41 UTC | Passed | 200 | 161 ms |
| 16 Oct 2026, 18:50 UTC | Passed | 200 | 193 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 10 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.