Is Crawlinx MCP down?
Down
Yes, Crawlinx MCP 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
- 12 h ago (19 Oct 2026, 06:02 UTC)
- Response time
- Not measured
- Next check
- In about 15 h
- How often
- About every 27 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 27 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 |
|---|---|---|---|
| 19 Oct 2026, 06:02 UTC | initialize returned HTTP 405 | 405 | 425 ms |
| 18 Oct 2026, 03:37 UTC | initialize returned HTTP 405 | 405 | 459 ms |
| 16 Oct 2026, 23:16 UTC | initialize returned HTTP 405 | 405 | 447 ms |
| 15 Oct 2026, 19:55 UTC | initialize returned HTTP 405 | 405 | 429 ms |
| 14 Oct 2026, 15:55 UTC | initialize returned HTTP 405 | 405 | 398 ms |
| 13 Oct 2026, 14:33 UTC | initialize returned HTTP 405 | 405 | 428 ms |
| 12 Oct 2026, 10:52 UTC | initialize returned HTTP 405 | 405 | 553 ms |
| 12 Oct 2026, 02:35 UTC | initialize returned HTTP 405 | 405 | 533 ms |
| 11 Oct 2026, 18:16 UTC | initialize returned HTTP 405 | 405 | 426 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 27 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.