Is Javelin Guardrails MCP Server down?
Down
Yes, Javelin Guardrails MCP Server is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize returned HTTP 405.
Latest check
- Last check
- 1 h ago (18 Oct 2026, 09:14 UTC)
- Response time
- Not measured
- Next check
- In about 27 h
- How often
- About every 28 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 28 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 |
|---|---|---|---|
| 18 Oct 2026, 09:14 UTC | initialize returned HTTP 405 | 405 | 61 ms |
| 17 Oct 2026, 05:00 UTC | initialize returned HTTP 405 | 405 | 82 ms |
| 15 Oct 2026, 23:35 UTC | initialize returned HTTP 405 | 405 | 94 ms |
| 14 Oct 2026, 19:47 UTC | initialize returned HTTP 405 | 405 | 56 ms |
| 13 Oct 2026, 18:20 UTC | initialize returned HTTP 405 | 405 | 49 ms |
| 12 Oct 2026, 12:55 UTC | initialize returned HTTP 405 | 405 | 72 ms |
| 12 Oct 2026, 03:16 UTC | initialize returned HTTP 405 | 405 | 58 ms |
| 11 Oct 2026, 18:04 UTC | initialize returned HTTP 405 | 405 | 58 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 28 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.