MySQL Ops MCP
NPM · MYSQL-OPS-MCP
MySQL MCP server: browse schema, query, CRUD. Delete/drop gated by user approval.
Available components
Last scanned (8 hours ago)
Scores higher than 36% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 10 of 25 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 111 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 421 tokens (~38/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 Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
- 55% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_data" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- CVE-2023-54404 affects this package: high ▼ security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +3
- CVE-2026-111769 affects this package: high ▼ security
- Stability: unverified → 0.27 ▲ functional
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-ops-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 3 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes | |
| 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 25 packages
| Packages resolved | 25 |
|---|---|
| Stale | 10 |
| 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 →
create_table ~36
创建新表
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | 数据库名称（可选） |
| sql | string | yes | CREATE TABLE语句 |
No output schema declared.
No examples provided.
delete_data ~46
删除表中的数据（需要授权）。此操作需要用户明确批准。
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | 数据库名称（可选） |
| sql | string | yes | DELETE语句 |
No output schema declared.
No examples provided.
describe_table ~37
查看表结构和字段信息
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | 数据库名称（可选） |
| table | string | yes | 表名 |
No output schema declared.
No examples provided.
drop_table ~48
删除表（需要授权）。此操作不可逆，需要用户明确批准。
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | 数据库名称（可选） |
| table | string | yes | 要删除的表名 |
No output schema declared.
No examples provided.
execute_sql ~44
执行自定义SQL语句（通用工具）
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | 数据库名称（可选） |
| sql | string | yes | SQL语句 |
No output schema declared.
No examples provided.
get_table_info ~44
获取表的详细信息，包括索引、约束等
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | 数据库名称（可选） |
| table | string | yes | 表名 |
No output schema declared.
No examples provided.
insert ~37
插入数据到表中
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | 数据库名称（可选） |
| sql | string | yes | INSERT语句 |
No output schema declared.
No examples provided.
list_databases ~18
列出所有可用的数据库
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tables ~37
列出指定数据库中的所有表
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | 数据库名称（可选，默认使用当前连接的数据库） |
No output schema declared.
No examples provided.
query ~39
执行SELECT查询语句
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | 数据库名称（可选） |
| sql | string | yes | SELECT查询语句 |
No output schema declared.
No examples provided.
update ~35
更新表中的数据
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | 数据库名称（可选） |
| sql | string | yes | UPDATE语句 |
No output schema declared.
No examples provided.
How do I install the MySQL Ops MCP server?
MySQL Ops MCP runs locally as an npm package, launched with npx -y mysql-ops-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-ops-mcp
claude mcp add gt-dinuo-mysql-ops-mcp -- npx -y mysql-ops-mcp
What is the MySQL Ops MCP server?
MySQL Ops MCP is listed in the public MCP registry as io.github.GT-dinuo/mysql-ops-mcp. MySQL MCP server: browse schema, query, CRUD. Delete/drop gated by user approval. This page covers its npm package (mysql-ops-mcp).
Is the MySQL Ops MCP server safe to use?
MySQL Ops MCP scores 68 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 Ops MCP server expose?
MySQL Ops MCP exposes 11 tools: list_databases, list_tables, describe_table, query, create_table, and 6 more. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.
Is the MySQL Ops MCP server still maintained?
MySQL Ops 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 Ops MCP server under?
MySQL Ops 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.