MySQL MCP Server (designcomputer)
Capped at 70: core tools not tested: no backing service on the test box; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested pypi mysql-mcp-server 0.4.5 (MIT; repo designcomputer/mysql_mcp_server). Installed pinned with scripts off (uv venv, Python 3.13) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 3 tools (3 annotated by the server: 2 read-only, 1 destructive). Real calls: 0 of 2 real function calls passed. No passing real call: needs a MySQL server and connection settings. Core tools not tested: 70 cap.
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): fail. 0 of 2 real function calls passed. No passing real call: needs a MySQL server and connection settings. Evidence: local test run, Nov 18, 2026 UTC.
Transport (tested 2026-11-18 UTC): stdio
Token cost (estimate): approx. 328 tokens, cl100k estimate (3 tools, measured 2026-11-18 UTC, version 0.4.5). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 2 read, 1 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
execute_sql— write (state-changing)get_schema_info— readget_table_sample— read
handshake and tools listed without a recorded key or OAuth
Score 70/100 · Tools 3 · Token cost approx. 328 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 0.4.5 · Package mysql-mcp-server · Repo designcomputer/mysql_mcp_server
Summary: MySQL MCP Server (designcomputer) completed an MCP handshake without credentials and exposed 3 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 3
- Context cost
- approx. 328 tokens, cl100k estimate (3 tools, measured 2026-11-18 UTC, version 0.4.5; an estimate) ranking · add up your servers' context cost
- API key
- No key to connect (handshake passed)
- Tested
- 2026-11-18 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | uv pip install mysql-mcp-server (Python venv, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 3 tools listed in 4.5s. |
| maintenance | pass | 25 | Repo pushed 20 days before test; 1,419 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (PyPI long_description (package README)). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 328 tokens, cl100k estimate for 3 tools · about 4% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-18 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 3 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-18 UTC test run; changes appear after the next test.
Note: tool list can depend on the connected database, so changes are annotated, not flagged automatically.
Snapshot hash (fingerprint of the tool list)
36357cc69eb2: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "mysql-mcp-server",
"version": "0.4.5",
"registry": "pypi",
"status": "working",
"tested": "2026-11-18",
"tools_count": 3,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`uv pip install mysql-mcp-server` (Python venv, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 3 tools listed in 4.5s."
],
"maintenance": [
"pass",
25,
"Repo pushed 20 days before test; 1,419 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (PyPI long_description (package README))."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
},
"testedAt": "2026-11-18T04:16:40.793Z"
}Install
uvx mysql-mcp-server
Pin the version we tested
uvx --from mysql-mcp-server==0.4.5 mysql_mcp_server
pip install mysql-mcp-server==0.4.5
tested 2026-11-18 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"mysql-mcp-server": {
"command": "uvx",
"args": [
"--from",
"mysql-mcp-server==0.4.5",
"mysql_mcp_server"
]
}
}
}Tools listed
execute_sql, get_schema_info, get_table_sample
Quick config
{
"mcpServers": {
"mysql-mcp-server": {
"command": "uvx",
"args": [
"mysql-mcp-server"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
uv pip install mysql-mcp-server(Python venv). This is the exact command we ran on 2026-11-18 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (3 in our test).
{
"mcpServers": {
"mysql-mcp-server": {
"command": "uvx",
"args": [
"mysql-mcp-server"
]
}
}
}Test history
- 2026-11-18 UTC: New
Related: Best database MCP servers
FAQ
Is MySQL MCP Server (designcomputer) deprecated?
No. MySQL MCP Server (designcomputer) was not deprecated or archived when we last tested it on 2026-11-18 UTC.
What replaces MySQL MCP Server (designcomputer)?
Nothing; MySQL MCP Server (designcomputer) is not deprecated as of 2026-11-18 UTC.
Does MySQL MCP Server (designcomputer) need an API key?
No. It completed an MCP handshake with no credentials and listed 3 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.