@sapiom/mcp@0.12.7
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 signal is a false positive: child_process is limited to opening the user-visible OAuth URL. Source shows package-aligned MCP, authentication, and telemetry behavior without a concrete malicious chain.
Decision evidence
public snapshot- At startup, retrieves MCP instructions from Sapiom's configured API.
- Each MCP tool invocation submits its arguments to the package analytics emitter.
- Explicit authentication opens a browser and exchanges an OAuth code via the configured API.
- No preinstall, install, or postinstall lifecycle hook is present.
- The browser child process only invokes platform URL openers with a generated OAuth URL.
- Credentials are read/written only for the explicit authenticate/logout flow with restrictive file modes.
- No source evidence of arbitrary command execution, harvesting, stealth persistence, or foreign agent-config mutation.
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.7.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.12.7 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.