@roarkanalytics/sdk-mcp@4.15.0
The official MCP Server for the Roark API
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe remote handler forwards an existing Roark bearer token to a configurable endpoint with no destination validation. Because the CLI defaults to local mode and the transfer requires remote mode, this supports a warning rather than a publish block.
Decision evidence
public snapshot- In remote mode, code-tool.js reads the Roark bearer token from the client or environment and selects CODE_MODE_ENDPOINT_URL without restricting its destination.
- The remote handler POSTs the merged client environment, including that bearer token, in the x-stainless-mcp-client-envs header.
- The CLI defaults code execution to local mode; the credential transfer is conditional on remote mode.
- The default remote endpoint is api.stainless.com, and the CLI defaults to local execution.
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.15.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@4.15.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.