@roarkanalytics/sdk-mcp@4.3.1
The official MCP Server for the Roark API
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe credential-forwarding path is active by default and the destination override is unrestricted. The inspected source does not establish an install-time or covert malware action.
Decision evidence
public snapshot- The server includes the code-execution tool by default and defaults it to the remote sandbox mode.
- The remote handler takes the Roark bearer token, combines it with request-provided client settings, and posts that data to an endpoint selected from an unrestricted environment variable.
- No npm install lifecycle hook was found.
- The inspected behavior is activated through the execute tool; no covert automatic send was identified.
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@4.3.1.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@4.3.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.