Is New Relic MCP Server down?
Up
No, New Relic MCP Server is up.
It passed its latest check 3 h ago in 444 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 3 h ago (16 Oct 2026, 20:49 UTC)
- Response time
- 444 ms (typical 447 ms)
- Next check
- In about 6 h
- How often
- About every 9 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 9 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 |
|---|---|---|---|
| 16 Oct 2026, 20:49 UTC | Passed | 401 | 444 ms |
| 16 Oct 2026, 10:14 UTC | Passed | 401 | 447 ms |
| 16 Oct 2026, 00:23 UTC | Passed | 401 | 427 ms |
| 15 Oct 2026, 15:04 UTC | Passed | 401 | 482 ms |
| 15 Oct 2026, 05:31 UTC | Passed | 401 | 498 ms |
| 14 Oct 2026, 19:44 UTC | Passed | 401 | 393 ms |
| 14 Oct 2026, 10:26 UTC | Passed | 401 | 458 ms |
| 14 Oct 2026, 01:26 UTC | Passed | 401 | 560 ms |
| 13 Oct 2026, 15:38 UTC | Passed | 401 | 441 ms |
| 13 Oct 2026, 06:52 UTC | Passed | 401 | 472 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 9 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.