@revoxai/sdk-mcp
The official MCP Server for the Revox API
This report shows the evidence for @revoxai/sdk-mcp@0.6.0. 1 of 2 known versions is blocked or flagged. The newest version, 0.7.0, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource directly establishes default remote transmission of credentials and user-supplied code to api.stainless.com. No install hook is involved, but the runtime exfiltration is sufficient for a block.
Decision evidence
public snapshot- The default execute tool selects a remote Stainless handler.
- That handler obtains REVOX_API_KEY from environment or client credentials.
- It POSTs serialized client environment values, submitted code, and intent to api.stainless.com.
- The MCP server enables the code tool by default.
- No npm preinstall, install, or postinstall lifecycle hook is declared.
- The executable only starts when invoked as the package CLI.
- A local execution mode exists, but remote execution is the default.
Source & flagged code
9 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
instructions.jsView on unpkgPackage source references dynamic require/import behavior.
instructions.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to @revoxai/sdk-mcp@0.6.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @revoxai/sdk-mcp@0.6.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.