MySQL ReadOnly MCP Server (zhaojw-php/mysql-readonly-mcp) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 4 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100
1 month ago

MySQL ReadOnly MCP Server

Enables AI assistants to safely query MySQL databases with read-only access, featuring SQL injection protection, connection pooling, and automatic query limits for secure database exploration.

→ zhaojw-php/mysql-readonly-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

zhaojw-php

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Known vulnerabilities in dependencies: 2 critical, 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: MYSQL_PASSWORD, MYSQL_SSL_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical2 high2 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalmysql2@3.6.5GHSA-4rch-2fh8-94vw

MySQL2 for Node Arbitrary Code Injection

criticalmysql2@3.6.5GHSA-fpw7-j2hg-69v5

mysql2 Remote Code Execution (RCE) via the readCodeFor function

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highmysql2@3.6.5GHSA-pmh2-wpjm-fj45

mysql2 vulnerable to Prototype Pollution

lowmysql2@3.6.5GHSA-49j4-86m8-q2jw

mysql2 vulnerable to Prototype Poisoning

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configMYSQL_DATABASEyour_database_name
configMYSQL_HOST"": "localhost",
🔐 secretMYSQL_PASSWORDyour_mysql_password
configMYSQL_PORT"": "3306",
configMYSQL_SSL_CA=path/to/ca.pem
configMYSQL_SSL_CERT=path/to/cert.pem
🔐 secretMYSQL_SSL_KEY=path/to/key.pem
configMYSQL_SSL_REJECT_UNAUTHORIZED❌ true 是否拒绝未授权的 SSL 证书
configMYSQL_USERyour_mysql_username
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

4/4 tools missing one or more hints — mysql_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mysql_list_tables (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mysql_describe_table (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 0/4 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Production dependencies are patched

2 critical, 2 high severity in production deps — mysql2@3.6.5 (critical), mysql2@3.6.5 (critical)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/zhaojw-php/mysql-readonly-mcp?variant=verified)](https://m8ven.ai/mcp/zhaojw-php/mysql-readonly-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 045abdba8e9e03d8fca396d85ac96448e4bb5b21
code hash: 72a7c64629a5b07c5fbce516535467ad6c7fdbb35631da772108244dc4f501fb
verified: 8/7/2026, 4:37:28 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client