@roarkanalytics/sdk-mcp@4.20.0
The official MCP Server for the Roark API
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe remote execution path can disclose an existing Roark bearer token to a configurable endpoint, so a credential-exposure warning is appropriate. The default CLI mode is local and the transfer is not shown to occur covertly by default, so the evidence does not support blocking.
Decision evidence
public snapshot- code-tool.js reads CODE_MODE_ENDPOINT_URL, falling back to the Stainless code-tool endpoint.
- The remote handler places the existing Roark bearer token in client environment data and POSTs it to the selected endpoint.
- The remote handler is reached when code execution mode is not local; server.js passes the request context and client into tool execution.
- The CLI defaults code execution to local Deno, and the code tool runs only when invoked.
- The source does not establish a package-selected unrelated recipient or a default transfer of credentials.
Source & flagged code
12 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
instructions.jsView on unpkgFindings
Affected versions and remediation
This report applies to @roarkanalytics/sdk-mcp@4.20.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@4.20.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.