@roarkanalytics/sdk-mcp@3.14.1
The official MCP Server for the Roark API
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe flagged credential-forwarding code is a legacy remote execution branch, while the shipped CLI defaults to local execution and rejects that mode. Source inspection found no install-time behavior or concrete malicious persistence, theft, or destructive action.
Decision evidence
public snapshot- A legacy remote code-tool branch can forward the Roark bearer token to api.stainless.com when explicitly selected.
- The worker dynamically evaluates code supplied to the MCP execute tool.
- Server instructions can be fetched from api.stainless.com.
- The manifest has no install lifecycle hook.
- The normal CLI defaults to local code execution and rejects the retired remote mode.
- The local worker scopes network access to the configured Roark API host.
- No persistence, destructive action, hidden payload, or automatic credential harvesting 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.14.1.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@3.14.1 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.