🟢 Remote MCP Live Status
Probed every 30 minutes with a real initialize handshake. Last updated 18m ago.
22Online
4Degraded
0Offline
0Not checked
26Total servers
| # | Server | Host | Status | Avg latency | 30d uptime | Last 30 checks | Last checked |
|---|---|---|---|---|---|---|---|
| 1 | official | Online | 7ms | 100% | 18m ago | ||
| 2 | official | Online | 10ms | 100% | 18m ago | ||
| 3 | official | Online | 11ms | 100% | 18m ago | ||
| 4 | official | Online | 14ms | 100% | 18m ago | ||
| 5 | official | Online | 26ms | 100% | 18m ago | ||
| 6 | official | Online | 37ms | 100% | 18m ago | ||
| 7 | official | Online | 40ms | 100% | 18m ago | ||
| 8 | official | Online | 41ms | 100% | 18m ago | ||
| 9 | official | Online | 42ms | 100% | 18m ago | ||
| 10 | official | Online | 58ms | 100% | 18m ago | ||
| 11 | official | Online | 61ms | 100% | 18m ago | ||
| 12 | official | Online | 62ms | 100% | 18m ago | ||
| 13 | official | Online | 62ms | 100% | 18m ago | ||
| 14 | community | Online | 73ms | 100% | 18m ago | ||
| 15 | official | Online | 108ms | 100% | 18m ago | ||
| 16 | official | Online | 208ms | 100% | 18m ago | ||
| 17 | official | Online | 229ms | 100% | 18m ago | ||
| 18 | official | Online | 232ms | 100% | 18m ago | ||
| 19 | gateway | Online | 302ms | 100% | 18m ago | ||
| 20 | official | Online | 305ms | 100% | 18m ago | ||
| 21 | community | Online | 310ms | 100% | 18m ago | ||
| 22 | gateway | Online | 511ms | 100% | 18m ago | ||
| 23 | official | Degraded | 8ms | 100% | 18m ago | ||
| 24 | gateway | Degraded | 103ms | 100% | 18m ago | ||
| 25 | official | Degraded | 166ms | 100% | 18m ago | ||
| 26 | official | Degraded | 228ms | 100% | 18m ago |
How we measure
- A cron worker probes each endpoint every 30 minutes with a real
initializeJSON-RPC request. - Online: public endpoints return a valid JSON-RPC response; OAuth-protected endpoints return the expected
401challenge. - Degraded: latency over 3 seconds, or a response that indicates a problem (unexpected redirect, missing JSON-RPC body).
- Offline: connection failure, timeout (10s), or 5xx.
Embed a live badge in your README — see any server page's Embed Status Badge section, e.g. /api/badge/status/linear.svg.