@sapiom/mcp@0.17.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 1mo ago · by lpm-firewall-aiStatic inspection found no lifecycle hook, self-dependency, stealth persistence, or concrete malicious behavior. Networked and destructive operations are aligned with the declared MCP service and are user-invoked.
Decision evidence
public snapshot- The manifest exposes a command entrypoint and contains no automatic install lifecycle hook.
- The browser authentication callback listens only on loopback.
- The destructive App Link deletion tool requires an explicit confirmation value.
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.17.0.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.17.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.