@roarkanalytics/sdk-mcp@4.9.0
The official MCP Server for the Roark API
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe configurable instruction endpoint forwards an existing credential without an allowlist, which is a concrete conditional credential-forwarding risk. The inspected manifest has no lifecycle hook or other active malicious chain.
Decision evidence
public snapshot- The manifest has no npm lifecycle hook; its listed scripts are development commands.
- Both CommonJS and ESM builds expose an execute MCP tool.
- The TypeScript source implements a local Deno execution handler.
- The worker evaluates supplied TypeScript through a data-module import.
- Instruction retrieval permits an environment-selected endpoint and forwards a Stainless authorization value.
- Local documentation search constructs in-memory MiniSearch indexes.
- No automatic install-time execution was found.
- The credential forwarding is conditional on a configured endpoint and a supplied Stainless key.
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.9.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@4.9.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.