MySQL Legacy MCP
NPM · MYSQL-LEGACY-MCP
Inspect and query MySQL 5.0–5.6; opt-in INSERT/UPDATE/DELETE/DDL. Live-verified 5.0–8.0.
Available components
Last scanned (11 hours ago)
Scores higher than 94% of npm servers
Category Databases
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 40 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Rufflet/mysql-legacy-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 51 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1020 tokens (~92/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/mysql-legacy-mcp@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Rufflet/mysql-legacy-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Rufflet/mysql-legacy-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 2830200940 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:141ea113e028206f5b41876feedcff5a7a5b2389b1870bd13a6c06d497dbe2b05dedc9a77329b4d3390d0459760b4b371dfe35ef75fae3da5693eb048 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 40 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
mysql_legacy_ddl ~110
Runs exactly one table-level CREATE, ALTER, DROP, TRUNCATE, or RENAME supplied in sql. Off unless MYSQL_LEGACY_ALLOW_DDL=true. DROP and TRUNCATE are irreversible. Rejects DROP DATABASE, views, and indexes. For row changes use mysql_legacy_insert, mysql_legacy_update, or mysql_legacy_delete.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | One MySQL table-level DDL statement: CREATE/ALTER/DROP/TRUNCATE/RENAME TABLE. |
No output schema declared.
No examples provided.
mysql_legacy_delete ~77
Runs exactly one DELETE supplied in sql. WHERE is required and cannot be disabled. Off unless MYSQL_LEGACY_ALLOW_DELETE=true. Returns affectedRows. To empty a table use TRUNCATE via mysql_legacy_ddl, not a WHERE-less DELETE.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | One MySQL DELETE statement with a WHERE clause. |
No output schema declared.
No examples provided.
mysql_legacy_describe_table ~108
Lists columns for database.table via SHOW FULL COLUMNS, including type, nullability, keys, comments, and collation. Use this for per-column metadata. For the full CREATE TABLE text and default charset use mysql_legacy_show_create_table. For index column order use mysql_legacy_list_indexes.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | yes | MySQL database name, 1–64 characters. |
| table | string | yes | MySQL table or view name, 1–64 characters. |
No output schema declared.
No examples provided.
mysql_legacy_insert ~87
Runs exactly one INSERT supplied in sql. Off unless MYSQL_LEGACY_ALLOW_INSERT=true. Returns insertId and affectedRows. INSERT ... ON DUPLICATE KEY UPDATE is accepted and can overwrite existing rows. For UPDATE/DELETE/DDL use mysql_legacy_update, mysql_legacy_delete, or mysql_legacy_ddl.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | One MySQL INSERT statement. |
No output schema declared.
No examples provided.
mysql_legacy_list_databases ~93
Lists database names via SHOW DATABASES. Hides mysql and information_schema unless include_system_databases=true (or MYSQL_LEGACY_HIDE_SYSTEM_DATABASES=false). Then pass a name to mysql_legacy_list_tables. Does not list tables or columns.
| Name | Type | Req | Description |
|---|---|---|---|
| include_system_databases | boolean | – | When true, include mysql and information_schema for this call. Overrides MYSQL_LEGACY_HIDE_SYSTEM_DATABASES. |
No output schema declared.
No examples provided.
mysql_legacy_list_indexes ~93
Lists indexes for database.table via SHOW INDEX (key name, columns, uniqueness, type). Use this for keys. For column types use mysql_legacy_describe_table; for full DDL use mysql_legacy_show_create_table.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | yes | MySQL database name, 1–64 characters. |
| table | string | yes | MySQL table or view name, 1–64 characters. |
No output schema declared.
No examples provided.
mysql_legacy_list_tables ~92
Lists base tables and views in one database via SHOW FULL TABLES FROM database. Pass database. For column types use mysql_legacy_describe_table; for CREATE TABLE text use mysql_legacy_show_create_table; for keys use mysql_legacy_list_indexes. To list databases first, use mysql_legacy_list_databases.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | yes | MySQL database name, 1–64 characters. |
No output schema declared.
No examples provided.
mysql_legacy_ping ~52
Checks the MySQL connection with SELECT VERSION() AS version and returns {connected, version}. Call this first after connecting. For schema use mysql_legacy_list_tables; for row data use mysql_legacy_select.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mysql_legacy_select ~132
Runs exactly one SELECT supplied in sql. Rejects SELECT INTO and locking reads; truncates by MYSQL_LEGACY_MAX_ROWS and MYSQL_LEGACY_MAX_RESULT_BYTES. On MySQL 5.6.5+ wraps in START TRANSACTION READ ONLY unless MYSQL_LEGACY_DISABLE_READ_ONLY_TRANSACTIONS=true. For columns use mysql_legacy_describe_table; for CREATE TABLE text use mysql_legacy_show_create_table; for writes use mysql_legacy_insert, mysql_legacy_update, or mysql_legacy_delete.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | One MySQL 5.1-compatible SELECT statement. |
No output schema declared.
No examples provided.
mysql_legacy_show_create_table ~96
Returns SHOW CREATE TABLE for database.table plus the parsed default charset. Use this for DDL text. For per-column types and collation use mysql_legacy_describe_table. For unique/non-unique keys use mysql_legacy_list_indexes.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | yes | MySQL database name, 1–64 characters. |
| table | string | yes | MySQL table or view name, 1–64 characters. |
No output schema declared.
No examples provided.
mysql_legacy_update ~80
Runs exactly one UPDATE supplied in sql. WHERE is required and cannot be disabled. Off unless MYSQL_LEGACY_ALLOW_UPDATE=true. Returns affectedRows and changedRows. To empty a table use TRUNCATE via mysql_legacy_ddl, not a WHERE-less UPDATE.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | One MySQL UPDATE statement with a WHERE clause. |
No output schema declared.
No examples provided.
How do I install the MySQL Legacy MCP server?
MySQL Legacy MCP runs locally as an npm package, launched with npx -y mysql-legacy-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mysql-legacy-mcp
claude mcp add rufflet-mysql-legacy-mcp -- npx -y mysql-legacy-mcp
What is the MySQL Legacy MCP server?
MySQL Legacy MCP is listed in the public MCP registry as io.github.Rufflet/mysql-legacy-mcp. Inspect and query MySQL 5.0–5.6; opt-in INSERT/UPDATE/DELETE/DDL. Live-verified 5.0–8.0. This page covers its npm package (mysql-legacy-mcp).
Is the MySQL Legacy MCP server safe to use?
MySQL Legacy MCP scores 91 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MySQL Legacy MCP server expose?
MySQL Legacy MCP exposes 11 tools: mysql_legacy_ping, mysql_legacy_select, mysql_legacy_insert, mysql_legacy_update, mysql_legacy_delete, and 6 more. Their descriptions and schemas cost roughly 1,020 tokens of context every time the server is loaded.
Is the MySQL Legacy MCP server still maintained?
MySQL Legacy MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MySQL Legacy MCP server under?
MySQL Legacy MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.