@sapiom/mcp@0.20.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 21d ago · by lpm-firewall-aiThe source inspection found no install hook or concrete attack behavior. Scanner findings correspond to browser OAuth, project scanning, and explicitly invoked App Link management.
Decision evidence
public snapshot- package.json points to the MCP server entrypoint and lists build and start scripts; no install lifecycle hook is present in the manifest.
- The scanner skips `.claude` and writes Git blobs beneath its supplied destination, rather than modifying agent configuration.
- The flagged process launch opens the browser for authentication; the authentication tool passes the resolved Sapiom app and API URLs to that flow.
- The token exchange sends an authorization code to the resolved API URL; production and staging defaults are Sapiom endpoints.
- App Link settings are changed through an explicit tool call, and deletion requires `confirm: true`.
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.1.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.20.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.