# MySQL MCP (npm · mcp-mysql-client)

MCP server for one MySQL database: schema, read-only queries and guarded writes.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `mcp-mysql-client`: 83/100 (this document), [markdown](https://verifymcp.io/servers/gistrec-mcp-mysql-client/mcp-mysql-client.md), [page](https://verifymcp.io/servers/gistrec-mcp-mysql-client/mcp-mysql-client)

## Channel facts

- Registry: `npm`
- Package: `mcp-mysql-client`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 34 of 104 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 29 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add gistrec-mcp-mysql-client -- npx -y mcp-mysql-client
```

### Cursor

```json
{
  "mcpServers": {
    "gistrec-mcp-mysql-client": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-mysql-client"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gistrec-mcp-mysql-client": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-mysql-client"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add gistrec-mcp-mysql-client -- npx -y mcp-mysql-client
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gistrec-mcp-mysql-client": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-mysql-client"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gistrec-mcp-mysql-client --command npx --arg -y --arg mcp-mysql-client
```

### Hermes

```yaml
mcp_servers:
  gistrec-mcp-mysql-client:
    command: "npx"
    args: ["-y", "mcp-mysql-client"]
```

### Netclaw

```json
{
  "McpServers": {
    "gistrec-mcp-mysql-client": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-mysql-client"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add gistrec-mcp-mysql-client -t stdio -c npx -a -y mcp-mysql-client
```

### Other

```json
{
  "mcpServers": {
    "gistrec-mcp-mysql-client": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-mysql-client"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 83, +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.

### 2026-09-18 (score 82, +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.

### 2026-09-16 (score 81, +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.

### 2026-09-14 (score 80, +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.

### 2026-09-12 (score 79, +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.

### 2026-09-10 (score 78, +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.

### 2026-09-08 (score 77, +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.

### 2026-09-06 (score 76, +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.

## MCP tools (6)

### `server_info` (~102 tokens)

Сведения о подключении и правах

Показывает, к какой базе и под каким пользователем подключён сервер, версию MySQL, размер базы, выданные пользователю права (GRANT) и действующие ограничения самого MCP-сервера: разрешённые операции записи, потолок строк в ответе и таймаут запроса. Стоит вызвать первым, если непонятно, почему запрос отклонён: права MySQL и разрешения сервера — это два независимых ограничения.

### `list_tables` (~94 tokens)

Список таблиц базы

Перечисляет таблицы и представления подключённой базы: движок, кодировку, комментарий, размер данных и индексов в байтах и оценку числа строк. Оценка берётся из статистики InnoDB и может заметно расходиться с реальностью — точное число даёт COUNT(*) через query. С этого инструмента стоит начинать знакомство с незнакомой базой.

### `describe_table` (~163 tokens)

Структура таблицы

Показывает структуру таблицы: столбцы с типами, обнуляемостью, значениями по умолчанию и комментариями, индексы с их составом, внешние ключи наружу и, главное, ссылки на эту таблицу из других (referenced_by) — именно они определяют, безопасно ли удалять строки. Разделы, кроме столбцов, можно отключить, если нужен только их список.

Input parameters:

- `include_foreign_keys` (boolean): Включить внешние ключи в обе стороны (по умолчанию да).
- `include_indexes` (boolean): Включить индексы (по умолчанию да).
- `table` (string, required): Имя таблицы в подключённой базе данных.

### `query` (~184 tokens)

Выполнить читающий SQL-запрос

Выполняет один читающий запрос (SELECT, SHOW, DESCRIBE, WITH ... SELECT) и возвращает строки. Изменяющие запросы отклоняются даже при включённых правах на запись — для них есть execute. Запрос идёт внутри read-only транзакции, число строк ограничено MYSQL_MAX_ROWS: если ответ обрезан, поле truncated равно true и это префикс, а не весь результат. Значения подставляйте через ? и params — драйвер экранирует их сам.

Input parameters:

- `limit` (integer): Максимум строк в ответе. Потолок задан MYSQL_MAX_ROWS и не повышается этим полем.
- `params` (array): Значения для подстановки вместо ? в порядке появления.
- `sql` (string, required): Один SQL-запрос. Несколько инструкций через ; не выполняются.

### `explain` (~178 tokens)

Показать план выполнения запроса

Возвращает план выполнения читающего запроса: какие индексы будут использованы и сколько строк сервер рассчитывает просмотреть. Обычный режим ничего не выполняет; analyze=true запускает запрос по-настоящему и показывает фактическое время — на больших таблицах это дорого. Полезно перед тяжёлой выборкой и при диагностике медленных запросов.

Input parameters:

- `analyze` (boolean): Выполнить запрос и показать фактические строки и время (EXPLAIN ANALYZE).
- `format` (string): Формат плана: traditional — таблица, json — подробное дерево, tree — читаемое дерево.
- `params` (array): Значения для подстановки вместо ? в порядке появления.
- `sql` (string, required): Один SQL-запрос. Несколько инструкций через ; не выполняются.

### `execute` (~215 tokens)

Выполнить изменяющий SQL-запрос

Выполняет один изменяющий запрос — 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.

Input parameters:

- `allow_full_table` (boolean): Подтверждение для UPDATE или DELETE без WHERE и LIMIT — такой запрос затрагивает всю таблицу.
- `params` (array): Значения для подстановки вместо ? в порядке появления.
- `sql` (string, required): Один SQL-запрос. Несколько инструкций через ; не выполняются.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/gistrec-mcp-mysql-client/mcp-mysql-client#diagnostics

## Score history

- 2026-09-21: 83
- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 79
- 2026-09-12: 79
- 2026-09-11: 78
- 2026-09-10: 78
- 2026-09-09: 77
- 2026-09-08: 77
- 2026-09-07: 76
- 2026-09-06: 76
- 2026-09-05: 75
- 2026-09-04: 75
- 2026-09-03: 75
- 2026-09-02: 74
- 2026-09-01: 74
- 2026-08-31: 73
- 2026-08-30: 69
- 2026-08-29: 69
- 2026-08-28: 69
- 2026-08-27: 69
- 2026-08-26: 69
- 2026-08-25: 68
- 2026-08-24: 68
- 2026-08-23: 53

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/mcp-mysql-client
- Socket report: https://socket.dev/npm/package/mcp-mysql-client
- Repository: https://github.com/gistrec/mcp-mysql-client
- Changelog RSS feed: https://verifymcp.io/servers/gistrec-mcp-mysql-client/mcp-mysql-client.xml
- Changelog JSON feed: https://verifymcp.io/servers/gistrec-mcp-mysql-client/mcp-mysql-client.json
- HTML version of this page: https://verifymcp.io/servers/gistrec-mcp-mysql-client/mcp-mysql-client