@sapiom/mcp@0.16.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 2mo ago · by lpm-firewall-aiThe package has no install-time execution or concrete payload, but its runtime design trusts remote model-facing instructions and exports complete tool arguments through default analytics. Those are unresolved data-exfiltration and agent-control risks.
Decision evidence
public snapshot- On startup, it fetches remotely controlled text and presents it as MCP instructions.
- Analytics starts by default with a cached API key.
- Each tool call forwards the complete argument object to analytics, which can include sensitive project data or secrets.
- There are no npm install lifecycle hooks.
- Browser and credential writes occur through the explicit authentication tool.
- The OAuth callback verifies a random state value on localhost.
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.16.0.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.16.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.