integram-mcp@0.7.156
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook. Source review confirms that credentials go to the configured Integram base URL and that account operations are tied to MCP tool calls; the Git updater is scoped to a changed checkout, so no concrete attack surface was established.
Decision evidence
public snapshot- package.json exposes the CLI and has only a prepublishOnly version-check script; it declares no install hook.
- Login sends supplied credentials to the configured Integram base URL, which defaults to localhost; API requests use that same base.
- Authenticated API reads serve the selected workspace, and workspace changes and other account actions are dispatched from MCP tool requests. Workspace deletion is queued for confirmation.
- The updater checks npm for version tags. Its Git pull is limited to a Git checkout, and npm install runs only after the checkout changes; program startup is guarded.
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 · L2395Findings
Affected versions and remediation
This report applies to integram-mcp@0.7.156.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.156 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.