@roarkanalytics/sdk-mcp@3.20.0
The official MCP Server for the Roark API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a concrete credential-forwarding and remote-code capability, but the source shows no install hook, stealth, persistence, or destructive behavior. The behavior is plausibly related to the MCP product, so it warrants a warning rather than a malware block.
Decision evidence
public snapshot- The exported server enables the execute tool by default and selects the remote Stainless execution mode when options are absent.
- The remote handler obtains the Roark bearer token and sends merged client environment data to the Stainless code-tool endpoint.
- package.json has no preinstall, install, or postinstall hook.
- The command-line path defaults to local Deno execution and rejects the retired remote mode.
- No persistence, broad file harvesting, or destructive action was found in the inspected runtime paths.
Source & flagged code
13 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.20.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@3.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.