@roarkanalytics/sdk-mcp@3.23.0
The official MCP Server for the Roark API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a real dangerous MCP capability, but the inspected source contains no install-time execution, persistence, stealth, destructive behavior, or autonomous exfiltration. The local execution path is explicit server functionality with a restricted network allowlist, so the evidence does not establish malware.
Decision evidence
public snapshot- The default CLI enables a local code-execution mode.
- The code tool starts Deno with broad environment access and package-directory read access.
- The worker dynamically imports and invokes code supplied through the MCP execute tool.
- An alternate handler sends the Roark bearer token, submitted code, and client environment data to api.stainless.com.
- package.json has no preinstall, install, or postinstall hook.
- The executable runs only when invoked as the MCP server; importing it does not start the server.
- The local sandbox restricts network access to the configured Roark API hostname.
- No package source writes agent configuration, persists itself, or performs destructive actions.
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.23.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@3.23.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.