pintumcp@1.2.0
Agent Alerts MCP — desktop notifications with sound for AI coding agents
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe automatic postinstall changes existing AI-agent configuration files so they can load this package's server. This meets the install-time control-surface mutation block criterion.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package through npm, which runs its postinstall script.
Impact
Agent applications may load the package's server without a separate explicit configuration command.
Mechanism
The installer detects supported agent configuration files and writes a pintumcp server entry into each detected configuration.
Policy narrative
During npm installation, the postinstall script launches the CLI's install command. That command detects existing agent configuration files and adds a server entry pointing to this package's Python notification service. This is an unconsented install-time mutation of foreign agent control settings.
AI rationale
The automatic postinstall changes existing AI-agent configuration files so they can load this package's server. This meets the install-time control-surface mutation block criterion.
Evidence
package.jsoninstall.jsbin/pintumcp.jslib/detect.jslib/configure.js
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 97.0% confidence with low false-positive risk.
Evidence for policy risk
- package.json starts a postinstall script that runs install.js.
- install.js automatically runs the CLI install command during postinstall.
- The install command configures every detected tool, including existing agent settings under the user's home directory.
- The configuration code writes updated settings files; the added MCP server runs this package's Python notification server.
Evidence against
- The configured server exposes desktop notification and sound tools; inspected source shows no credential collection or network endpoint.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg10"postinstall": "node install.js"
},
"keywords": [
"mcp",
"notifications",
"agent",
"alerts",
"claude",
"codex",
"opencode",
"mimocode",
"antigravity"
],
"li
High
Suspicious Lifecycle Evidence
package.json starts a postinstall script that runs install.js.
package.jsonView on unpkg · L10•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpython/server.pyView file
Findings
6 High4 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSuspicious Lifecycle Evidencepackage.json
HighSuspicious Lifecycle Evidenceinstall.js
HighAi Review Evidencebin/pintumcp.js
HighAi Review Evidencelib/detect.js
HighAi Review Evidencelib/configure.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Build Helperpython/server.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to pintumcp@1.2.0.
See all versions of pintumcp for other recorded verdicts.
- Avoid installing pintumcp@1.2.0. 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.