registry / @roarkanalytics/sdk-mcp / 3.2.0

@roarkanalytics/sdk-mcp@3.2.0

The official MCP Server for the Roark API

AI Security Review

scanned 1mo ago · by lpm-firewall-ai

This is an official Stainless-generated Roark MCP server with no install hooks. Scanner labels for token forwarding and template similarity describe documented Code Mode, not a hidden exfiltration path.

Static reason

High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source

Trigger

User runs the mcp-server binary or npx package; there are no npm install lifecycle hooks.

Impact

No unconsented install-time or import-time attack is present.

Mechanism

User-invoked MCP Code Mode with optional Stainless-hosted sandbox

AI rationale

Decision evidence

public snapshot

AI called this Clean at 90.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

Default execute tool posts ROARK_API_BEARER_TOKEN to api.stainless.com for Stainless-hosted sandboxes.
Local Deno worker evaluates agent TypeScript via a data URL import when code-execution-mode is local.
Scanner similarity matches Stainless-generated MCP template files, not unique malware.

Evidence against

package.json has no preinstall, install, or postinstall scripts; the mcp-server bin starts only when the user runs it.
This is the official Roark MCP server generated by Stainless; live hosts are api.stainless.com and api.roark.ai.
CLI documents --code-execution-mode stainless-sandbox versus local; token forwarding is required for the advertised remote sandbox.
Worker eval and docs search run only after explicit MCP tool use, not at npm install or import.
No persistence, destructive writes, dependency confusion, or agent-config mutation was found.

Behavioral surface

Source

ChildProcessDynamicRequireEnvironmentVarsFilesystemNetwork

Source & flagged code

11 flagged

instructions.jsView file

Lines 1-27javascript

1"use strict";

2// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.

3var __importDefault = (this && this.__importDefault) || function (mod) {

4 return (mod && mod.__esModule) ? mod : { "default": mod };

5};

6Object.defineProperty(exports, "__esModule", { value: true });

7exports.getInstructions = getInstructions;

8const promises_1 = __importDefault(require("fs/promises"));

9const logger_1 = require("./logger.js");

Medium

Dynamic Require

Package source references dynamic require/import behavior.

instructions.jsView on unpkg · L7

10const util_1 = require("./util.js");

11const INSTRUCTIONS_CACHE_TTL_MS = 15 * 60 * 1000; // 15 minutes

12const instructionsCache = new Map();

13async function getInstructions({ stainlessApiKey, customInstructionsPath, }) {

14 const now = Date.now();

15 const cacheKey = customInstructionsPath ?? stainlessApiKey ?? '';

16 const cached = instructionsCache.get(cacheKey);

17 if (cached && now - cached.fetchedAt <= INSTRUCTIONS_CACHE_TTL_MS) {

18 return cached.fetchedInstructions;

19 }

20 // Evict stale entries so the cache doesn't grow unboundedly.

21 for (const [key, entry] of instructionsCache) {

22 if (now - entry.fetchedAt > INSTRUCTIONS_CACHE_TTL_MS) {

23 instructionsCache.delete(key);

24 }

25 }

26 let fetchedInstructions;

27 if (customInstructionsPath) {

•matchType = normalized_sha256 matchedPackage = plumery-mcp@3.9.0 matchedPath = instructions.js matchedIdentity = npm:cGx1bWVyeS1tY3A:3.9.0 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

instructions.jsView on unpkg

code-tool.jsView file

Lines 31-71javascript

31 if (mod != null) for (var k = ownKeys(mod), i = 0; i < k.length; i++) if (k[i] !==

package.jsonView file

Lines 207-235json

207 "import": "./types.mjs",

208 "require": "./types.js"

209 },

210 "./types.js": {

211 "default": "./types.js"

212 },

213 "./types.mjs"

code-tool.mjsView file

•matchType = normalized_sha256 matchedPackage = @roarkanalytics/sdk-mcp@3.6.1 matchedPath = code-tool.mjs matchedIdentity = npm:QHJvYXJrYW5hbHl0aWNzL3Nkay1tY3A:3.6.1 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

code-tool.mjsView on unpkg

src/code-tool.tsView file

•matchType = normalized_sha256 matchedPackage = @roarkanalytics/sdk-mcp@3.6.1 matchedPath = src/code-tool.ts matchedIdentity = npm:QHJvYXJrYW5hbHl0aWNzL3Nkay1tY3A:3.6.1 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

src/code-tool.tsView on unpkg

code-tool-worker.jsView file

•matchType = normalized_sha256 matchedPackage = @roarkanalytics/sdk-mcp@3.6.1 matchedPath = code-tool-worker.js matchedIdentity = npm:QHJvYXJrYW5hbHl0aWNzL3Nkay1tY3A:3.6.1 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

code-tool-worker.jsView on unpkg

local-docs-search.jsView file

•matchType = token_shingles matchedPackage = @roarkanalytics/sdk-mcp@3.24.0 matchedPath = local-docs-search.js matchedIdentity = npm:QHJvYXJrYW5hbHl0aWNzL3Nkay1tY3A:3.24.0 similarity = 1.000 shingleOverlap = 48 summary = source token shingles overlapped finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

local-docs-search.jsView on unpkg

Source & flagged code

11 flagged · loading source

instructions.jsView file

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

instructions.jsView on unpkg

7exports.getInstructions = getInstructions; L8: const promises_1 = __importDefault(require("fs/promises")); L9: const logger_1 = require("./logger.js");

Medium

Dynamic Require

Package source references dynamic require/import behavior.

instructions.jsView on unpkg · L7

code-tool.jsView file

51Source sends the broad process environment to a literal external destination. L51: interfaceType: 'PHONE', L52: recordingUrl: 'https://example.com', L53: startedAt: 'startedAt', ... L154: }, L155: body: JSON.stringify({ L156: project_name: 'roark-analytics', ... L165: } L166: throw new Error(`${res.status}: ${res.statusText} error when trying to contact Code Tool server. Details: ${await res.text()}`); L167: } ... L193: // Check if deno is in PATH L194: const { execSync } = await Promise.resolve().then(() => __importStar(require('node:child_process'))); L195: try {

Findings

2 Critical7 High5 Medium4 Low

CriticalHardcoded Runtime Data Exfiltrationcode-tool.js

CriticalManifest Confusionpackage.json

HighKnown Malware Source Similaritycode-tool.js

HighKnown Malware Source Similaritycode-tool.mjs

HighKnown Malware Source Similaritysrc/code-tool.ts

HighKnown Malware Source Similaritycode-tool-worker.js

HighKnown Malware Source Similarityinstructions.js

HighKnown Malware Source Similaritylocal-docs-search.js

HighPrevious Version Dangerous Deltacode-tool.js

MediumDynamic Requireinstructions.js

MediumNetwork

MediumEnvironment Vars

Affected versions and remediation

This report applies to @roarkanalytics/sdk-mcp@3.2.0.

See all versions of @roarkanalytics/sdk-mcp for other recorded verdicts.

Review the evidence and your use of @roarkanalytics/sdk-mcp@3.2.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: 2026-09-17 02:20:16.043Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.