@sapiom/mcp@0.19.2
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 29d ago · by lpm-firewall-aiThe scanner’s reverse-shell and agent-configuration hints do not match the inspected behavior: the process call opens a browser, and the `.claude` reference only skips that directory. The package manifest has no install lifecycle hook, and the inspected authentication and app-management behavior is consistent with its CLI purpose.
Decision evidence
public snapshot- package.json defines a CLI entry point and has no install lifecycle script.
- The `.claude` directory appears in a scanner skip list; this location does not configure an agent.
- The browser process is launched by the authentication flow, which stores credentials returned by that flow.
- Authentication exchanges a code with the configured Sapiom API endpoint.
- The flagged app-management code registers a tool for changing published App Link settings.
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.19.2.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.19.2 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.