@roarkanalytics/sdk-mcp@3.30.0
The official MCP Server for the Roark API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource inspection does not establish malicious intent or install-time abuse, but it does establish a credential-forwarding remote default for library consumers. Treat it as a high-risk vulnerability requiring a warning.
Decision evidence
public snapshot- The exported tool selector defaults callers without options to the retired remote Stainless execution mode.
- That remote mode sends the Roark bearer token and caller-supplied upstream environment values to api.stainless.com.
- The CLI explicitly defaults to local Deno execution and rejects the remote mode.
- There are no npm install lifecycle hooks.
- The network behavior is part of the MCP code-execution feature, not hidden import-time activity.
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 unpkgPackage source references dynamic require/import behavior.
instructions.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to @roarkanalytics/sdk-mcp@3.30.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@3.30.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.