@sapiom/mcp@0.13.1
Local Sapiom developer MCP server (sapiom-dev) — the unmetered surface for building and operating on Sapiom; today it scaffolds, tests, deploys, and inspects orchestrations. Not the remote Sapiom capability MCP.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe flagged process operation is a browser opener for OAuth, not a reverse shell. The package has no lifecycle hook and its file and network operations are feature-aligned and user-invoked.
Decision evidence
public snapshot- The authentication helper launches a platform browser opener.
- The app-publish tool reads selected project files and uploads a bundle when its MCP tool is invoked.
- Startup can fetch mutable authoring instructions from the vendor API.
- package.json has no preinstall, install, postinstall, or self-dependency.
- The child-process use only opens the OAuth URL; no shell command or remote command is executed.
- OAuth binds its callback server to loopback and exchanges a user login code with the configured API.
- Project reads and publishing occur only through named MCP tools, with cached credentials.
- No credential harvesting, broad configuration mutation, persistence, destructive action, or payload execution was found.
Source & flagged code
7 flaggedSource matches reverse-shell style process and socket wiring.
dist/auth.jsView on unpkg · L1A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
Findings
Affected versions and remediation
This report applies to @sapiom/mcp@0.13.1.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.13.1 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.