MySQL MCP
NPM · MCP-MYSQL-CLIENT · SCANNED SEP 21
MCP server for one MySQL database: schema, read-only queries and guarded writes.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 104 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 29 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1342 tokens (~223/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 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
How do I install the MySQL MCP server?
MySQL MCP runs locally as an npm package, launched with npx -y mcp-mysql-client. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-mysql-client
claude mcp add gistrec-mcp-mysql-client -- npx -y mcp-mysql-client
{
"mcpServers": {
"gistrec-mcp-mysql-client": {
"command": "npx",
"args": [
"-y",
"mcp-mysql-client"
]
}
}
} {
"servers": {
"gistrec-mcp-mysql-client": {
"command": "npx",
"args": [
"-y",
"mcp-mysql-client"
]
}
}
} codex mcp add gistrec-mcp-mysql-client -- npx -y mcp-mysql-client
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gistrec-mcp-mysql-client": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-mysql-client"
],
"enabled": true
}
}
} openclaw mcp add gistrec-mcp-mysql-client --command npx --arg -y --arg mcp-mysql-client
mcp_servers:
gistrec-mcp-mysql-client:
command: "npx"
args: ["-y", "mcp-mysql-client"] {
"McpServers": {
"gistrec-mcp-mysql-client": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-mysql-client"
]
}
}
} assistant mcp add gistrec-mcp-mysql-client -t stdio -c npx -a -y mcp-mysql-client
{
"mcpServers": {
"gistrec-mcp-mysql-client": {
"command": "npx",
"args": [
"-y",
"mcp-mysql-client"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Analysed npm/mcp-mysql-client@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 →
Dependencies 104 packages
| Packages resolved | 104 |
|---|---|
| Stale | 34 |
| 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 →
describe_table Структура таблицы ~163
Показывает структуру таблицы: столбцы с типами, обнуляемостью, значениями по умолчанию и комментариями, индексы с их составом, внешние ключи наружу и, главное, ссылки на эту таблицу из других (referenced_by) — именно они определяют, безопасно ли удалять строки. Разделы, кроме столбцов, можно отключить, если нужен только их список.
| Name | Type | Req | Description |
|---|---|---|---|
| include_foreign_keys | boolean | – | Включить внешние ключи в обе стороны (по умолчанию да). |
| include_indexes | boolean | – | Включить индексы (по умолчанию да). |
| table | string | yes | Имя таблицы в подключённой базе данных. |
No output schema declared.
No examples provided.
execute Выполнить изменяющий SQL-запрос ~215
Выполняет один изменяющий запрос — INSERT, UPDATE, DELETE или REPLACE — и возвращает число затронутых строк. Сейчас сервер разрешает: только чтение. Права выдаются переменными ALLOW_INSERT_OPERATION, ALLOW_UPDATE_OPERATION и ALLOW_DELETE_OPERATION в конфигурации MCP-клиента и требуют перезапуска сервера — из диалога их получить нельзя. DDL (CREATE, ALTER, DROP, TRUNCATE) не поддерживается ни при каких настройках. Запрос выполняется сразу и без транзакции: откатить его отсюда нельзя. UPDATE и DELETE без WHERE и LIMIT требуют явного allow_full_table=true.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_full_table | boolean | – | Подтверждение для UPDATE или DELETE без WHERE и LIMIT — такой запрос затрагивает всю таблицу. |
| params | array | – | Значения для подстановки вместо ? в порядке появления. |
| sql | string | yes | Один SQL-запрос. Несколько инструкций через ; не выполняются. |
No output schema declared.
No examples provided.
explain Показать план выполнения запроса ~178
Возвращает план выполнения читающего запроса: какие индексы будут использованы и сколько строк сервер рассчитывает просмотреть. Обычный режим ничего не выполняет; analyze=true запускает запрос по-настоящему и показывает фактическое время — на больших таблицах это дорого. Полезно перед тяжёлой выборкой и при диагностике медленных запросов.
| Name | Type | Req | Description |
|---|---|---|---|
| analyze | boolean | – | Выполнить запрос и показать фактические строки и время (EXPLAIN ANALYZE). |
| format | string | – | Формат плана: traditional — таблица, json — подробное дерево, tree — читаемое дерево. |
| params | array | – | Значения для подстановки вместо ? в порядке появления. |
| sql | string | yes | Один SQL-запрос. Несколько инструкций через ; не выполняются. |
No output schema declared.
No examples provided.
list_tables Список таблиц базы ~94
Перечисляет таблицы и представления подключённой базы: движок, кодировку, комментарий, размер данных и индексов в байтах и оценку числа строк. Оценка берётся из статистики InnoDB и может заметно расходиться с реальностью — точное число даёт COUNT(*) через query. С этого инструмента стоит начинать знакомство с незнакомой базой.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query Выполнить читающий SQL-запрос ~184
Выполняет один читающий запрос (SELECT, SHOW, DESCRIBE, WITH ... SELECT) и возвращает строки. Изменяющие запросы отклоняются даже при включённых правах на запись — для них есть execute. Запрос идёт внутри read-only транзакции, число строк ограничено MYSQL_MAX_ROWS: если ответ обрезан, поле truncated равно true и это префикс, а не весь результат. Значения подставляйте через ? и params — драйвер экранирует их сам.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Максимум строк в ответе. Потолок задан MYSQL_MAX_ROWS и не повышается этим полем. |
| params | array | – | Значения для подстановки вместо ? в порядке появления. |
| sql | string | yes | Один SQL-запрос. Несколько инструкций через ; не выполняются. |
No output schema declared.
No examples provided.
server_info Сведения о подключении и правах ~102
Показывает, к какой базе и под каким пользователем подключён сервер, версию MySQL, размер базы, выданные пользователю права (GRANT) и действующие ограничения самого MCP-сервера: разрешённые операции записи, потолок строк в ответе и таймаут запроса. Стоит вызвать первым, если непонятно, почему запрос отклонён: права MySQL и разрешения сервера — это два независимых ограничения.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the MySQL MCP server?
MySQL MCP is listed in the public MCP registry as io.github.gistrec/mcp-mysql-client. MCP server for one MySQL database: schema, read-only queries and guarded writes. This page covers its npm package (mcp-mysql-client).
Is the MySQL MCP server safe to use?
MySQL MCP scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 MCP server expose?
MySQL MCP exposes 6 tools: server_info, list_tables, describe_table, query, explain, execute. Their descriptions and schemas cost roughly 936 tokens of context every time the server is loaded.
Is the MySQL MCP server still maintained?
MySQL MCP is still listed as active in the MCP registry. We last reached this channel on 21 September 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 MCP server under?
MySQL 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.