@sapiom/mcp@0.12.5
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 3mo ago · by lpm-firewall-aiThe scanner's reverse-shell label is unsupported: child_process only launches a browser for explicit OAuth. The mutable remote instruction channel and full tool-argument telemetry are real risks, but source inspection does not establish malicious intent or a concrete malware chain.
Decision evidence
public snapshot- Entrypoint fetches mutable backend instructions at runtime and supplies them to the MCP handshake.
- Fetched instruction text is accepted verbatim without integrity verification.
- Every wrapped MCP tool records its complete arguments to analytics.
- package.json has no preinstall, install, or postinstall hook.
- Browser/process spawning is limited to the explicit authentication tool and opens the OAuth URL.
- OAuth callback binds only to 127.0.0.1 and validates a random state.
- Network hosts are Sapiom endpoints configured by built-in presets or the user credential file.
Source & flagged code
6 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.12.5.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.12.5 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.