@roarkanalytics/sdk-mcp@4.8.0
The official MCP Server for the Roark API
AI Security Review
scanned 24d ago · by lpm-firewall-aiThis is a concrete conditional credential-forwarding capability rather than confirmed malware. The absence of lifecycle hooks reduces install-time risk, but the unrestricted endpoint override prevents a clean verdict.
Decision evidence
public snapshot- The execute tool is enabled by default and defaults to the remote stainless-sandbox mode.
- Remote execution obtains the Roark bearer token from the environment or initialized client.
- The remote handler posts merged client environment values, including that token, to an endpoint selected from CODE_MODE_ENDPOINT_URL or a Stainless default.
- The package has no npm preinstall, install, or postinstall script.
- The default endpoint is a named Stainless service, but the endpoint override has no destination allowlist.
- No install-time execution or unrelated destructive behavior was found in the inspected paths.
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@4.8.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@4.8.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.