mcp-mysql-client

MCPcommunity
v1.0.0io.github.gistrecUnknownUpdated 1mo agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Reads these credentials
  • MYSQL_PASSAPI keyoptional

    Password for that user. Treat it as a secret; MYSQL_PASS_FILE reads it from a file instead.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.gistrec
LicenseUnknown
Version1.0.0
Sourcenpm+mcp-registry
npmmcp-mysql-client
GitHubgistrec/mcp-mysql-client
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv1.0.0 · 28d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagev1.0.0 · 28d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

queryВыполняет один читающий запрос (SELECT, SHOW, DESCRIBE, WITH ... SELECT) и возвращает строки.

Выполняет один читающий запрос (SELECT, SHOW, DESCRIBE, WITH ... SELECT) и возвращает строки.

No input schema was published for this tool.

explainВозвращает план выполнения читающего запроса: какие индексы будут использованы и сколько строк

Возвращает план выполнения читающего запроса: какие индексы будут использованы и сколько строк

No input schema was published for this tool.

list_tablesПеречисляет таблицы и представления подключённой базы: движок, кодировку, комментарий, размер

Перечисляет таблицы и представления подключённой базы: движок, кодировку, комментарий, размер

No input schema was published for this tool.

describe_tableПоказывает структуру таблицы: столбцы с типами, обнуляемостью, значениями по умолчанию и

Показывает структуру таблицы: столбцы с типами, обнуляемостью, значениями по умолчанию и

No input schema was published for this tool.

server_infoПоказывает, к какой базе и под каким пользователем подключён сервер, версию MySQL, размер базы,

Показывает, к какой базе и под каким пользователем подключён сервер, версию MySQL, размер базы,

No input schema was published for this tool.

executeВыполняет один изменяющий запрос — INSERT, UPDATE, DELETE или REPLACE — и возвращает число

Выполняет один изменяющий запрос — INSERT, UPDATE, DELETE или REPLACE — и возвращает число

No input schema was published for this tool.

6 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

6 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-15 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

64 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+52 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in databases