Is useqr-mcp down?
Up
No, useqr-mcp is up.
It passed its latest check 7 h ago in 420 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 7 h ago (16 Oct 2026, 11:20 UTC)
- Response time
- 420 ms (typical 358 ms)
- Next check
- In about 2 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 |
|---|---|---|---|
| 16 Oct 2026, 11:20 UTC | Passed | 200 | 420 ms |
| 16 Oct 2026, 01:47 UTC | Passed | 200 | 358 ms |
| 15 Oct 2026, 15:50 UTC | Passed | 200 | 288 ms |
| 15 Oct 2026, 06:03 UTC | Passed | 200 | 299 ms |
| 14 Oct 2026, 20:14 UTC | Passed | 200 | 338 ms |
| 14 Oct 2026, 10:47 UTC | Passed | 200 | 348 ms |
| 14 Oct 2026, 01:09 UTC | Passed | 200 | 260 ms |
| 13 Oct 2026, 16:19 UTC | Passed | 200 | 1.2 s |
| 13 Oct 2026, 07:07 UTC | Passed | 200 | 710 ms |
| 12 Oct 2026, 22:17 UTC | Passed | 200 | 544 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.