Is an MCP server down? How we tell
Yesterday, , we judged the day of 37,415 servers from our own checks. This is how they came out.
| Day | What it means | Servers |
|---|---|---|
| Up | Every counted check answered. | 33,208 |
| Slow or briefly down | Five minutes of down time at most, or a slow or partly broken answer. | 37 |
| Down | More than five minutes of down time. | 4,134 |
| Our trouble | The failures were on our side, so they say nothing about the server. | 36 |
How we decide
- One failed check is not down time. Down time starts only when the next check fails too, and lasts until a check answers again.
- A failed check is repeated five minutes later, and every five minutes for the first hour of an outage.
- In an hour where more than 20% of at least 20 checks failed across the servers that had been answering, the failures count as our trouble.
- A day with fewer than 90% of its planned checks gets no verdict.
Each server's page shows its last 90 days, and its README can carry a live badge of its uptime.