@roarkanalytics/sdk-mcp@3.28.0
The official MCP Server for the Roark API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package is not shown to be malware, but it provides a real, high-impact code-execution capability to MCP callers and includes a credential-forwarding remote execution path. It should be warned on rather than blocked because the behavior is product-aligned and not automatically triggered at installation.
Decision evidence
public snapshot- The MCP server enables its code-execution tool by default.
- The worker evaluates caller-supplied TypeScript and invokes the exported function.
- Local execution grants the worker environment access and forwards the host environment plus client-provided variables.
- The library-only remote mode sends the Roark bearer token and merged client environment data to api.stainless.com.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The normal CLI defaults to local Deno execution and scopes network access to the configured Roark API host.
- No persistence, destructive filesystem action, or concealed payload was found.
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.28.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@3.28.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.