registry  /  apidash-mcp  /  1.0.1

apidash-mcp@1.0.1

Standalone Model Context Protocol (MCP) server bridge for API Dash

AI Security Review

scanned 3h ago · by lpm-firewall-ai

No confirmed malicious attack surface, but runtime use can download and execute a native API Dash engine and exposes MCP HTTP-request execution tools. This is user-invoked via the bin entry, not install-time mutation.

Static reason
One or more suspicious static signals were detected.
Trigger
running npx apidash-mcp or the apidash-mcp bin
Impact
AI client can cause API Dash engine to execute user-specified HTTP requests; downloaded native code runs locally
Mechanism
runtime native binary download/extraction and MCP bridge execution
Rationale
Source inspection shows a documented MCP bridge with runtime binary acquisition and HTTP execution capability, but no concrete malicious behavior or unconsented install-time agent control mutation. The unresolved risk is the user-invoked native payload download/execution path, so warn rather than block.
Evidence
package.jsonindex.jsREADME.mdbin/bin/bundle.zipbin/apidash.exe
Network endpoints1
github.com/AbdelrahmanELBORGY/apidash/releases/download/v1.0.0-mcp/apidash-windows-mcp.zip

Decision evidence

public snapshot
AI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
  • index.js runtime fallback downloads a GitHub release zip and extracts it into bin/.
  • index.js executes downloaded/local API Dash binary with --mcp-engine.
  • index.js exposes MCP tools that can execute HTTP requests through API Dash.
  • index.js uses execSync for unzip/PowerShell extraction, PATH lookup, help validation, and taskkill cleanup.
Evidence against
  • package.json has no preinstall/install/postinstall lifecycle scripts.
  • Network URL is package-aligned: github.com/AbdelrahmanELBORGY/apidash release asset.
  • No source evidence of credential harvesting, env dumping, persistence, or stealth exfiltration.
  • Child process use is for locating, validating, launching, and cleaning up the API Dash engine.
  • README.md documents the MCP bridge, APIDASH_PATH override, and fallback GitHub release download.
Behavioral surface
Source
ChildProcessEnvironmentVarsFilesystemNetwork
Supply chain
HighEntropyStringsUrlStrings
ManifestNo manifest risk signals triggered.
scanned 1 file(s), 9.50 KB of source, external domains: github.com

Source & flagged code

2 flagged · loading source
index.jsView file
2L3: const { spawn, execSync } = require('child_process'); L4: const path = require('path');
High
Child Process

Package source references child process execution.

index.jsView on unpkg · L2
2L3: const { spawn, execSync } = require('child_process'); L4: const path = require('path'); ... L7: const os = require('os'); L8: const https = require('https'); L9: ... L11: if (process.argv.includes('--help') || process.argv.includes('-h')) { L12: process.stdout.write(` L13: 🚀 API Dash MCP Server (v1.0.0)
High
Command Output Exfiltration

Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.

index.jsView on unpkg · L2

Findings

2 High2 Medium3 Low
HighChild Processindex.js
HighCommand Output Exfiltrationindex.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings