mysql-mcp (raviraj-ntp/mysql-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 61 tools. No publisher has claimed this listing.

C
Emerging
74/100
21 days ago

mysql-mcp

Feature-rich MCP server for MySQL and MariaDB with multi-connection support. Connect many instances at once — query schemas, run scripts, test stored procedures with sandbox rollback.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

raviraj-ntp

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 →

Install from

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

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// 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_CONNECTION_FILTER
configMYSQL_DEFAULT_CONNECTION
configMYSQL_EXPLAIN_CHECK
configMYSQL_EXTRA_CONNECTIONSstaging:MYSQL_URI_STAGING,prod:MYSQL_URI_PROD
configMYSQL_MAX_ROWS
configMYSQL_MCP_CONFIG
configMYSQL_QUERY_TIMEOUT_MS
configMYSQL_READ_ONLY
configMYSQL_TEST_SANDBOX_DEFAULT
configMYSQL_URI"": "mysql://user:pass@localhost:3306"
// 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

61/61 tools missing one or more hints — execute_ddl (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_database (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); drop_database (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +58 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 inputs are validated

46/61 tool handlers declare input schemas (75%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Domain consistency

npm scope @raviraj87 doesn't match GitHub owner raviraj-ntp

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 5 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 Score](https://m8ven.ai/badge/mcp/raviraj-ntp/mysql-mcp)](https://m8ven.ai/mcp/raviraj-ntp/mysql-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2a11f0b42fc9b940d5546dda5c1c3e04fd847172
code hash: f5201647c5263676074120a23101bb0f98af5bfd5043b4476e0ffcca8b86e060
verified: 8/21/2026, 1:29:40 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