opsinsight-mcp@0.3.1
VERIFIED· not startedPublisher claims: "Read-only MCP server for support ticket investigation across PostgreSQL, AWS CloudWatch and New Relic" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso newrelic.com, attacker.example — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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 82/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 deviationsStatic findings
monkeypatch.setenv("NEW_RELIC_ACCOUNT_ID", "") # beats any value in a local .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# have the old AWS_* names set in their environment/.env and get no signal thatFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Uses ``_env_file=None`` so pydantic-settings does not read ``.env``.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.``AKIAIOSFODNN7EXAMPLE`` → ``AKIA...PLE``.Fix: Never read or enumerate credential locations; accept a documented environment variable instead.message="NEW_RELIC_API_KEY and NEW_RELIC_ACCOUNT_ID must be set (in .env or the MCP client config's env block).",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.over AWS_PROFILE when set in .env; falling back further to boto3'sFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file = tmp_path / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.assert mask_key("AKIAIOSFODNN7EXAMPLE") == "AKIA...PLE"Fix: Never read or enumerate credential locations; accept a documented environment variable instead.Cost to the agent
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 opsinsight-mcp@0.3.1 as of 14 h ago. This is the package itself, not its dependencies.