integram-mcp@0.7.144
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe scanner’s execution hints correspond to a self-update path activated when the command runs, not an install hook. The inspected behavior updates the package’s own Git checkout, while the account actions found are exposed through the MCP server for user invocation.
Decision evidence
public snapshot- package.json exposes index.js as a command-line entry point and has no install lifecycle hook; prepublishOnly only runs a version check.
- The automatic updater runs at server startup and hourly, and only attempts a fast-forward Git update in the package directory; changed code triggers dependency installation and a restart.
- Update checks request npm package version tags from the configured registry; the default is registry.npmjs.org.
- Login sends caller-configured Integram credentials to the configured Integram server. The cited subscription actions are exposed as MCP tools for user invocation.
- Runtime self-updating and running npm install after a Git update are powerful behaviors, but the inspected path is limited to updating the package’s own Git checkout.
Source & flagged code
3 flagged · loading sourceThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
index.jsView on unpkgPackage source invokes a package manager install command at runtime.
index.jsView on unpkg · L2377Findings
Affected versions and remediation
This report applies to integram-mcp@0.7.144.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.144 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.