io.github.karldane/newrelic-mcp

New Relic MCP

Is the New Relic MCP server down? Yes. It has given no valid answer since 2026-10-31: install failed.

New Relic MCP server with 55 tools for APM, alerts, dashboards, synthetics, workflows, and more.

install failed down since 2026-10-31 · probed 2026-11-15 · unchanged since 2026-11-07

not a zip file: [/tmp/mcpcost-stdio-b0MQFg/bundle.mcpb]
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes

Bundle: https://github.com/karldane/newrelic-mcp/releases/download/v1.0.1/newrelic-mcp-linux-amd64.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
Host: github.com
Repository: https://github.com/karldane/newrelic-mcp
Registry: active, updated 2026-06-20 · registry entry

Compare this server with others.

More servers

Other registry entries on github.com, the ones next to this name; all of them.

K8s MCP Server (Go) io.github.kaneg/k8s-mcp-go · crashed on start
kapaweb deploy io.github.kapaweb/kapaweb-deploy · alive
Cicadas local MCP io.github.kevinwowo/cicadas-local-mcp · needs env
keyline io.github.keyline-dev/keyline · crashed on start
io.github.kiki830621/che-apple-mail-mcp · install failed
macOS Calendar & Reminders io.github.kiki830621/che-ical-mcp · crashed on start
io.github.kOlapsis/gofact · crashed on start
JMAP mail io.github.kOlapsis/jmap-mcp · crashed on start

Servers that mention newrelic.

New Relic MCP Server com.newrelic/mcp-server · needs auth
New Relic MCP Server io.github.newrelic-partners/mcp-server · needs auth
New Relic MCP Server io.github.Meet-Bhalodiya/newrelic-mcp · needs args
io.github.newrelic-experimental/preflight · needs env

Badge for the README

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

No valid answer since 2026-10-31, in every probe since then.
npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.