@roarkanalytics/sdk-mcp@3.26.0
The official MCP Server for the Roark API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe source does not establish stealth malware or install-hook abuse, but it exposes code execution and forwards credentials to an external service when that handler is used. This warrants a warning for dangerous MCP capability rather than a publish block.
Decision evidence
public snapshot- The remote code tool forwards the Roark bearer token and caller-supplied environment values to api.stainless.com.
- The default MCP tool set exposes an execute tool, and its local mode starts Deno with environment access before dynamically importing supplied code.
- The package contains no install lifecycle hook, but this is a high-impact runtime capability for an MCP server.
- The npm manifest has no preinstall, install, or postinstall hook.
- The CLI defaults to local execution and restricts Deno network access to the configured API host and worker socket.
- No hidden persistence, destructive file operation, or unrelated network receiver was found in the inspected source.
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.26.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@3.26.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.