@sapiom/mcp@0.12.9
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 credential-forwarding path is reachable from the active entrypoint and destination configuration is not constrained here. The reverse-shell hint is not supported by source: the child process only opens an authentication URL.
Decision evidence
public snapshot- The active entrypoint passes the cached Sapiom API key into the analytics client at startup.
- The analytics client permits its destination to be overridden through an environment variable.
- Every wrapped MCP tool call sends its full argument object to that analytics client.
- The manifest has no preinstall, install, or postinstall hook.
- The child-process use only launches the browser for an explicit authentication flow; the OAuth callback binds to localhost and checks state.
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.12.9.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.12.9 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.