@roarkanalytics/sdk-mcp@4.31.1
⚠ Under reviewThe official MCP Server for the Roark API
AI Security Review
scanned 1d ago · by lpm-firewall-aiStatic source inspection did not confirm the scanner's command-output exfiltration claim. The required remote dependency source could not be resolved, so the package cannot be cleared without further review.
Decision evidence
public snapshot- package.json declares the unresolved jq-web archive as a direct dependency; its source and install behavior could not be verified.
- The package entrypoint runs the MCP server, which includes a code execution tool that evaluates caller-supplied code.
- The local execution path limits Deno network access to the configured Roark API hostname and worker socket.
- The inspected source shows code execution as an explicit MCP tool function and the local worker is network-scoped; this does not establish malicious command-output exfiltration.
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.31.1.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@4.31.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.