@sapiom/mcp@0.15.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 scanner's reverse-shell match is a false positive: auth.js only launches the platform browser opener and handles a local OAuth callback. There are no install hooks or automatic project/config mutations, and the remaining sensitive operations are explicit authenticated MCP tools.
Decision evidence
public snapshot- The MCP server fetches current authoring instructions from the configured Sapiom API when it starts.
- The authentication flow opens a browser and runs a loopback callback server before exchanging an OAuth code.
- A delete tool can remove a hosted App Link, but it requires an explicit true confirmation and authenticated credentials.
- package.json has no preinstall, install, postinstall, or self-dependency.
- The child-process use is limited to opening the browser for the user-authentication flow.
- Credential storage is limited to the package-owned .sapiom credential file with restrictive permissions.
- Publishing and management operations are registered MCP tools, not install-time actions.
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.15.0.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.15.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.