Is New Relic MCP Server down?
Up
No, New Relic MCP Server is up.
It passed its latest check 6 h ago in 487 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 6 h ago (16 Oct 2026, 18:46 UTC)
- Response time
- 487 ms (typical 433 ms)
- Next check
- In about 3 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, 18:46 UTC | Passed | 401 | 487 ms |
| 16 Oct 2026, 08:18 UTC | Passed | 401 | 514 ms |
| 15 Oct 2026, 22:22 UTC | Passed | 401 | 404 ms |
| 15 Oct 2026, 13:05 UTC | Passed | 401 | 426 ms |
| 15 Oct 2026, 02:54 UTC | Passed | 401 | 484 ms |
| 14 Oct 2026, 17:22 UTC | Passed | 401 | 483 ms |
| 14 Oct 2026, 07:35 UTC | Passed | 401 | 408 ms |
| 13 Oct 2026, 21:52 UTC | Passed | 401 | 463 ms |
| 13 Oct 2026, 12:50 UTC | Passed | 401 | 419 ms |
| 13 Oct 2026, 03:56 UTC | Passed | 401 | 414 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.