@roarkanalytics/sdk-mcp@3.5.0
The official MCP Server for the Roark API
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has a concrete, default-path transfer of an API bearer token and arbitrary caller environment values to a third-party remote executor, plus unvalidated remote instruction loading. These are serious runtime risks but do not establish stealthy malware or an install-time attack chain.
Decision evidence
public snapshot- The default remote code tool sends the Roark bearer token and caller-supplied environment values to api.stainless.com.
- The MCP server fetches remote instructions at startup and supplies them to connected AI clients without validation.
- The package exposes code execution by default, increasing the impact of the remote credential transfer.
- package.json has no install or postinstall lifecycle hook.
- The network actions are part of named MCP documentation and code-execution tools; no persistence, destructive action, or hidden payload was found.
- The local execution path restricts network access to the configured Roark API host.
Source & flagged code
11 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.5.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@3.5.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.