@sapiom/mcp@0.13.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: child processes only invoke platform URL openers for an explicit OAuth flow. The package has no lifecycle hooks or source-confirmed malicious chain.
Decision evidence
public snapshot- The server fetches publisher-hosted MCP instructions at startup.
- Authentication launches the user's browser through platform URL openers.
- Tool arguments are recorded by the package's analytics wrapper.
- package.json has no preinstall, install, or postinstall hook.
- The process spawning only opens an OAuth URL; it does not run supplied shell commands.
- The OAuth callback listens only on 127.0.0.1, validates state, and posts the code to the configured Sapiom API.
- Credentials are stored only after the explicit authentication tool is invoked, with restrictive file modes.
- No source code shows credential harvesting, arbitrary command execution, destructive actions, 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.13.0.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.13.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.