@roarkanalytics/sdk-mcp@4.22.1
⚠ Under reviewThe official MCP Server for the Roark API
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe inspected runtime code shows user-invoked code execution and a local sandbox path, but no confirmed attack behavior. The remote dependency source remains unresolved, so this review cannot establish a clean result.
Decision evidence
public snapshot- package.json declares jq-web from a remote GitHub release archive; its source could not be resolved in this review.
- The MCP server includes code execution by default, but the inspected option parser rejects the retired remote sandbox mode, while local execution runs through a Deno worker with restricted network access.
- The remote execution handler can send the Roark bearer token to the Stainless endpoint, but the inspected entrypoint’s mode checks prevent confirming that path is reachable.
- The package manifest has no install lifecycle hook.
- The entrypoint starts the MCP server only when run as the main module.
- The local execution path restricts worker network access to the Roark API host and its Unix socket.
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.22.1.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@4.22.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.