Skills/PyPI/newrelic-mcp-server

newrelic-mcp-server@1.3.2

VERIFIED· not started

Publisher claims: "New Relic MCP Server - Model Context Protocol server for New Relic APIs" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher piekstra · publishing for 463 daysInstalls 1,602Last detonated 33 h ago
$claude mcp add newrelic-mcp-server -- uvx newrelic-mcp-server
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
NEW_RELIC_API_KEYNEWRELIC_API_KEYConfiguration, not credentials: NEWRELIC_ACCOUNT_ID, NEWRELIC_REGION
Where it talks to
newrelic.com (its own)
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for NEW_RELIC_API_KEY, NEWRELIC_API_KEY and talks to newrelic.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets NEW_RELIC_API_KEY=newrelic.com,NEWRELIC_API_KEY=newrelic.com -- uvx newrelic-mcp-server

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 89/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsnewrelic_mcp/server.py:15 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesfrom .credentials import SecureCredentialsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

No other findings across 3,455 lines in 19 files.

Cost to the agent

Instructions loaded
≈58 tok
1 file · 19 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for newrelic-mcp-server@1.3.2 as of 31 h ago. This is the package itself, not its dependencies.

newrelic-mcp-server@1.3.2 safety verdict: Verified (not started) — KillerSkills