@sapiom/mcp@0.20.0
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 25d ago · by lpm-firewall-aiDirect inspection found no install hook or concrete malicious behavior. The scanner's agent-configuration hint identifies a skipped directory, while the flagged process use is consistent with the package's browser authentication and project-scanning functions.
Decision evidence
public snapshot- package.json exposes the MCP entrypoint and command; it has no install lifecycle hook.
- The flagged project scanner skips common generated and fixture directories and bounds discovery depth.
- The authentication code exchanges a browser-returned authorization code with the configured API URL.
- App management reads credentials and only sends a settings update when the caller supplies changes.
- The inspected authentication code uses a local callback and sends the authorization code to the configured API URL; the flagged process use is consistent with browser launch and project scanning.
- The agent-configuration hint points to a directory exclusion in the scanner, not a write to agent configuration.
Source & flagged code
5 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.20.0.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.20.0 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.