@roarkanalytics/sdk-mcp@4.25.1
⚠ Under reviewThe official MCP Server for the Roark API
AI Security Review
scanned 3d ago · by lpm-firewall-aiInspected source shows an exposed, caller-invoked API code execution feature and its remote credential-forwarding flow, but no independent concrete attack was confirmed. Because required dependency source could not be resolved, the package cannot be cleared as clean from this inspection.
Decision evidence
public snapshot- The manifest declares a remote jq-web archive dependency and a TypeScript runtime dependency; the available dependency review could not resolve their source.
- The MCP server enables its code tool by default and uses a remote Stainless sandbox by default; the local mode runs submitted code in a Deno worker.
- Remote mode sends the Roark bearer token and submitted code to the configured endpoint, which defaults to the Stainless code tool service.
- The worker evaluates submitted code and collects its logs as results; local Deno network access is scoped to the Roark API host.
- The package manifest has no install or lifecycle hooks.
- Inspected code shows command execution and evaluation within the user-invoked code tool, with the local worker's network access scoped to the Roark API host.
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 unpkgFindings
Affected versions and remediation
This report applies to @roarkanalytics/sdk-mcp@4.25.1.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@4.25.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.