Is Lex Ops MCP down?
Up
No, Lex Ops MCP is up.
It passed its latest check 3 h ago in 803 ms. It has passed every check since 6 Nov 2026, 13:51 UTC.
Latest check
- Last check
- 3 h ago (10 Nov 2026, 08:27 UTC)
- Response time
- 803 ms (typical 1.1 s)
- Next check
- In about 8 h
- How often
- About every 12 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 12 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 |
|---|---|---|---|
| 10 Nov 2026, 08:27 UTC | Passed | 401 | 803 ms |
| 9 Nov 2026, 21:15 UTC | Passed | 401 | 1.0 s |
| 9 Nov 2026, 10:20 UTC | Passed | 401 | 1.1 s |
| 8 Nov 2026, 23:38 UTC | Passed | 401 | 1.2 s |
| 8 Nov 2026, 11:26 UTC | Passed | 401 | 1.6 s |
| 7 Nov 2026, 23:55 UTC | Passed | 401 | 936 ms |
| 7 Nov 2026, 12:46 UTC | Passed | 401 | 2.1 s |
| 7 Nov 2026, 00:04 UTC | Passed | 401 | 1.1 s |
| 6 Nov 2026, 13:51 UTC | Passed | 401 | 1.6 s |
| 6 Nov 2026, 01:46 UTC | initialize returned HTTP 405 | 405 | 938 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 12 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.