Is Mcp Registry Changes down?
Up
No, Mcp Registry Changes is up.
It passed its latest check 2 min ago in 113 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 2 min ago (23 Oct 2026, 12:01 UTC)
- Response time
- 113 ms (typical 424 ms)
- Next check
- In about 4 h
- How often
- About every 4 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 4 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 |
|---|---|---|---|
| 23 Oct 2026, 12:01 UTC | Passed | 402 | 113 ms |
| 23 Oct 2026, 07:07 UTC | Passed | 402 | 120 ms |
| 23 Oct 2026, 02:17 UTC | Passed | 402 | 96 ms |
| 22 Oct 2026, 21:27 UTC | Passed | 402 | 395 ms |
| 22 Oct 2026, 16:37 UTC | Passed | 402 | 291 ms |
| 22 Oct 2026, 12:03 UTC | Passed | 402 | 408 ms |
| 22 Oct 2026, 07:37 UTC | Passed | 402 | 420 ms |
| 22 Oct 2026, 03:20 UTC | Passed | 402 | 129 ms |
| 21 Oct 2026, 23:18 UTC | Passed | 402 | 575 ms |
| 21 Oct 2026, 19:18 UTC | Passed | 402 | 368 ms |
Price and payment address
- Price
- $0.02 per call on Base
- Pays to
- 0x6334…3039
No price or payment address changes recorded.
How we check
Up means the endpoint answered an unpaid test request with a valid x402 payment challenge. We never pay, so we can't see whether the paid response works.
Checks come from our server, about every 4 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. To see what an agent gets right now, check it yourself.