@roarkanalytics/sdk-mcp@4.19.0
The official MCP Server for the Roark API
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe programmatic server API defaults to hosted execution and forwards the Roark bearer token to api.stainless.com. The CLI defaults to local execution and rejects hosted mode, so this is a conditional credential exposure rather than evidence of malicious intent.
Decision evidence
public snapshot- The exported server API includes the code tool by default and selects stainless-sandbox when codeExecutionMode is omitted.
- In non-local mode, the handler selects api.stainless.com as the default endpoint and sources ROARK_API_BEARER_TOKEN from the environment or SDK client.
- The handler sends merged client environment values in the x-stainless-mcp-client-envs request header.
- The package exposes the server module; its normal CLI defaults to local execution and rejects stainless-sandbox.
- The regular CLI path defaults to local execution and rejects the hosted mode.
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.19.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@4.19.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.