@roarkanalytics/sdk-mcp@4.10.0
The official MCP Server for the Roark API
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe package has an unresolved credential-forwarding risk because an existing service credential can be sent to an unrestricted configured endpoint. Static inspection found no install hook or separate evidence of malicious intent.
Decision evidence
public snapshot- The package declares ordinary build and test scripts, with no install lifecycle hook.
- The MCP server includes the code-execution tool by default and selects remote execution by default.
- The remote endpoint is configurable through an environment variable while the Roark bearer token is taken from environment or the active client.
- The request sends the merged client environment, including that bearer token, to the selected endpoint.
- The built-in endpoint is a named Stainless service rather than an unrelated hidden host.
- No install-time mutation, persistence, or destructive behavior was found.
Source & flagged code
11 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.10.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@4.10.0 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.