@roarkanalytics/sdk-mcp@3.33.0
The official MCP Server for the Roark API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiScanner malice labels come from a shared Stainless MCP template and leftover remote-sandbox code, not from a hidden exfil or install hook. The published CLI defaults to local Deno execution, rejects the retired Stainless sandbox, and has no lifecycle scripts.
Decision evidence
public snapshot- code-tool.js still has a retired remote handler that would POST ROARK_API_BEARER_TOKEN to api.stainless.com when execution mode is not local.
- The same remote handler is present in code-tool.mjs and src/code-tool.ts.
- instructions.js GETs MCP prompt text from api.stainless.com when the server starts.
- code-tool-worker.js dynamically imports agent-supplied TypeScript in the local Deno worker.
- local-docs-search.js is a large generated Roark API docs index; the scanner treated that Stainless MCP template as malware-similar.
- package.json has no preinstall, install, or postinstall scripts; the only bin is user-run mcp-server.
- CLI defaults code-execution-mode to local and throws if stainless-sandbox is requested, so the published entrypoint does not send the Roark token to Stainless.
- Docs search defaults to the shipped local MiniSearch index, not the hosted Stainless search API.
- Network hosts are vendor-aligned (api.stainless.com, api.roark.ai) and there is no obfuscation, persistence, or agent-config write.
- Scanner similarity is shared Stainless MCP server code, not a unique hidden payload.
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@3.33.0.
See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.
- Review the evidence and your use of @roarkanalytics/sdk-mcp@3.33.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.