integram-mcp@0.7.151
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 npm install lifecycle hook, and source inspection found no concrete attack behavior. The package-manager command is part of a conditional runtime Git updater; authentication and account operations target the configured service and explicit tool actions.
Decision evidence
public snapshot- The manifest exposes index.js as the CLI and has no preinstall, install, or postinstall hook.
- Login sends caller-provided credentials to the configured service; authenticated API requests use the same configured base URL.
- Workspace changes are exposed as tool calls, and deleting a workspace requires a separate confirmation.
- Startup update checks run from the CLI; the updater acts only in a Git checkout and installs dependencies only after the checkout changes.
- The source includes child-process and package-manager commands, but they belong to conditional Git-based runtime updating rather than an npm install hook.
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 · L2388Findings
Affected versions and remediation
This report applies to integram-mcp@0.7.151.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.151 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.