nife-mcp-server@1.0.4
VERIFIED· startup onlyPublisher claims: "Model Context Protocol server for Nife.io GraphQL API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
NIFE_ACCESS_TOKENConfiguration, not credentials: PYTHON- Where it talks to
- no vendor host named in the codeAlso nife.io — 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
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names nife.io as well as its own vendor. The guard injects NIFE_ACCESS_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
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 (3 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-13 and scored it 90/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 · 20 s · 3 scenarios · 0 deviationsStatic findings
-----END PGP PUBLIC KEY BLOCK-----Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.echo " chmod +x bin/nife-mcp-server.js"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.chmod +x update_claude_config.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.run: chmod +x bin/nife-mcp-server.jsFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.chmod +x run_server.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.chmod +x bin/nife-mcp-server.jsFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.echo " npx @nife/mcp-server"Fix: Pin versions and sources; vendor anything fetched at install time.chmod +x release.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.chmod +x cleanup.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.chmod +x RELEASE_SUMMARY.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.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 nife-mcp-server@1.0.4 as of 31 h ago. This is the package itself, not its dependencies.