Is Command+K down?
Up
No, Command+K is up.
It passed its latest check 6 h ago in 624 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 6 h ago (25 Oct 2026, 03:50 UTC)
- Response time
- 624 ms (typical 980 ms)
- Next check
- In about 4 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 |
|---|---|---|---|
| 25 Oct 2026, 03:50 UTC | Passed | 401 | 624 ms |
| 24 Oct 2026, 15:54 UTC | Passed | 401 | 1.2 s |
| 24 Oct 2026, 04:55 UTC | Passed | 401 | 742 ms |
| 23 Oct 2026, 18:39 UTC | Passed | 401 | 1.2 s |
| 23 Oct 2026, 08:06 UTC | Passed | 401 | 767 ms |
| 22 Oct 2026, 21:31 UTC | Passed | 401 | 1.2 s |
| 22 Oct 2026, 11:25 UTC | Passed | 401 | 884 ms |
| 22 Oct 2026, 01:57 UTC | Passed | 401 | 601 ms |
| 21 Oct 2026, 17:01 UTC | Passed | 401 | 148 ms |
| 21 Oct 2026, 07:10 UTC | Passed | 401 | 884 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.