Is Context crossmatch: compatibility typing for context ingestion down?
Up
No, Context crossmatch: compatibility typing for context ingestion is up.
It passed its latest check 11 h ago in 345 ms, and every check since we started checking it on 21 Oct 2026.
Latest check
- Last check
- 11 h ago (6 Nov 2026, 23:35 UTC)
- Response time
- 345 ms (typical 337 ms)
- Next check
- In about 2 h
- How often
- About every 13 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 13 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 |
|---|---|---|---|
| 6 Nov 2026, 23:35 UTC | Passed | 401 | 345 ms |
| 6 Nov 2026, 13:21 UTC | Passed | 401 | 350 ms |
| 6 Nov 2026, 00:48 UTC | Passed | 401 | 348 ms |
| 5 Nov 2026, 09:29 UTC | Passed | 401 | 364 ms |
| 4 Nov 2026, 18:56 UTC | Passed | 401 | 374 ms |
| 4 Nov 2026, 04:25 UTC | Passed | 401 | 108 ms |
| 3 Nov 2026, 13:46 UTC | Passed | 401 | 332 ms |
| 2 Nov 2026, 23:20 UTC | Passed | 401 | 328 ms |
| 2 Nov 2026, 09:51 UTC | Passed | 401 | 333 ms |
| 1 Nov 2026, 22:31 UTC | Passed | 401 | 337 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 13 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.