@neverinfamous/mysql-mcp
npm
v5.1.1
Source verified
Published by neverinfamous — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Enterprise-grade MySQL MCP Server with OAuth 2.1 authentication, connection pooling & tool filtering
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`dist/chunk-HKS2F7JC.js:951`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: s: require(), process., eval(), Function(), import(). Use mysql.* API instead.", category: ErrorCategory.VALIDATION,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/chunk-HKS2F7JC.js
In the server's implementation (`src/utils/error-suggestions.ts:395`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: s: require(), process., eval(), Function(), import(). Use mysql.* API instead.", category: ErrorCategory.VALIDATION,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/utils/error-suggestions.ts
In the server's implementation (`dist/chunk-W6C2YLTD.js:22`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: execSync, spawn } from 'child_process'; import { Buffer as Buffer$1 } from 'buffer'; import * as crypto2 from 'crypto';
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/chunk-W6C2YLTD.js
In the server's implementation (`src/adapters/mysql/tools/shell/common.ts:7`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from "child_process"; import { relative, resolve } from "path"; import * as path from "path"; import {
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/adapters/mysql/tools/shell/common.ts
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/e2e/codemode.spec.ts:172`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ; test("should block eval()", async () => { const client = await createClient(); try { const p = await
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/e2e/codemode.spec.ts
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/test-cli-sessions.mjs:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; const delay = (ms) => new Promise(res => setTimeout(res, ms)); async function
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/test-cli-sessions.mjs
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/test-progress.mjs:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from "child_process"; import { resolve, dirname } from "path"; import { fileURLToPath } from "url"; c
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/test-progress.mjs
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/test-prompts.mjs:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from "child_process"; import { resolve, dirname } from "path"; import { fileURLToPath } from "url"; c
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/test-prompts.mjs
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/test-tool-annotations.mjs:25`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from "child_process"; // ============================================================================
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/test-tool-annotations.mjs
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/test-zod-errors.mjs:10`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from "child_process"; import { fileURLToPath } from "url"; import { dirname, join } from "path"; cons
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/test-zod-errors.mjs
In a packaging/dev/install script (shipped, but not the server runtime) (`src/adapters/mysql/tools/shell/__tests__/backup.test.ts:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: m "vitest"; import * as child_process from "child_process"; import { createMockRequestContext, createMockMySQLAdapte
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/adapters/mysql/tools/shell/__tests__/backup.test.ts
In a packaging/dev/install script (shipped, but not the server runtime) (`src/adapters/mysql/tools/shell/__tests__/common.test.ts:12`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from "child_process"; import { EventEmitter } from "events"; // Mock child_process vi.mock("child_pro
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/adapters/mysql/tools/shell/__tests__/common.test.ts
In a packaging/dev/install script (shipped, but not the server runtime) (`src/adapters/mysql/tools/shell/__tests__/data-transfer.test.ts:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: m "vitest"; import * as child_process from "child_process"; import { createMockRequestContext, createMockMySQLAdapte
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/adapters/mysql/tools/shell/__tests__/data-transfer.test.ts
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v5.1.1 latest |
A 94/100 | 13 | 1.13.0 | 2026-09-07 |
v5.0.0 |
A 94/100 | 13 | 1.12.1 | 2026-08-18 |
v4.0.0 |
A 94/100 | 13 | 1.12.1 | 2026-08-16 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @neverinfamous/mysql-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 70 side by side →
MySQL access with read-only guardrails, row caps, and statement timeouts.
A Model Context Protocol (MCP) server that provides LLMs with flexible, safe access to MySQL databases
MCP server for MySQL database operations
MySQL MCP Server - 通过 MCP 协议操作 MySQL 数据库
MySQL MCP Server - A Model Context Protocol server for MySQL database operations
MySQL MCP Server
Security scan results for the A5sql MCP server.
Expose AgentsKit tools as an MCP server — use them from Claude Desktop, Cursor, Windsurf, or any MCP host.
MCP server for Aiven cloud data platform - manage PostgreSQL, Kafka, and other services
MCP Server for All-Inkl.com hosting via KAS API
Structured aquarium, marine, terrarium and paludarium data for AI agents.
MCP server that gives your AI agent real vehicle data — specs, representative images, federal recalls, owner complaints, service bulletins, defect investigations, and OBD-II DTC reference — from the CarVector API.