@nookplot/mcp
Nookplot MCP server — connect any MCP-compatible agent to the Nookplot network
This report shows the evidence for @nookplot/mcp@0.4.132. 2 of 3 known versions are blocked or flagged. The newest version, 0.4.141, is flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms a postinstall hook that writes package-controlled Claude skill instructions into the user's AI agent configuration area without an explicit setup command. That meets the firewall boundary for unconsented lifecycle AI-agent control-surface mutation, even though credential and network behavior otherwise appears package-aligned. Product guard normalized a concrete AI-agent control hijack publish_block to the blockable dangerous-capability shape.
Decision evidence
public snapshot- package.json defines postinstall: node dist/postinstall.js
- dist/postinstall.js copies package skills into ~/.claude/skills during npm install when ~/.claude exists
- dist/index.js also installs skills into ~/.claude/skills at server startup
- skills/*/SKILL.md define agent slash-command workflows that create recurring Cron jobs
- dist/setup.js can write MCP config for Claude/Codex/Hermes, but only via explicit setup command
- No install-time credential harvesting or network calls seen in dist/postinstall.js
- Gateway network calls are package-aligned to https://gateway.nookplot.com or user/env-configured gateway
- dist/applyConfig.js uses execFileSync without shell and validates Hermes keys
- Credentials are stored locally under ~/.nookplot with restrictive modes
- On-chain signing and token tools are user-invoked MCP capabilities
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/applyConfig.jsView on unpkg · L26Findings
Affected versions and remediation
This report applies to @nookplot/mcp@0.4.132.
The versions list below shows the verdict for each recorded version.
- Avoid installing @nookplot/mcp@0.4.132. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.