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

C
Emerging
74/100
3 months ago

mcp-db-analyzer

A Model Context Protocol (MCP) server that gives AI assistants deep visibility into databases, inspecting schemas, detecting index problems, analyzing table bloat, and explaining query plans across PostgreSQL, MySQL, and SQLite.

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

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

Dmitriusan

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

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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.
🔐
You'll be asked for 2 credentials: DB_PASSWORD, MYSQL_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configDB_DRIVERYou can also set =mysql as an environment variable instead of passing the flag.
configDB_HOST
configDB_NAME
🔐 secretDB_PASSWORD
configDB_PATH
configDB_PORT
configDB_USER
configMYSQL_DATABASEOr use individual MySQL variables: MYSQL_HOST, MYSQL_PORT, , MYSQL_USER, MYSQL_PASSWORD.
configMYSQL_HOSTOr use individual MySQL variables: , MYSQL_PORT, MYSQL_DATABASE, MYSQL_USER, MYSQL_PASSWORD.
🔐 secretMYSQL_PASSWORDOr use individual MySQL variables: MYSQL_HOST, MYSQL_PORT, MYSQL_DATABASE, MYSQL_USER, .
configMYSQL_PORTOr use individual MySQL variables: MYSQL_HOST, , MYSQL_DATABASE, MYSQL_USER, MYSQL_PASSWORD.
configMYSQL_USEROr use individual MySQL variables: MYSQL_HOST, MYSQL_PORT, MYSQL_DATABASE, , MYSQL_PASSWORD.
configPGDATABASEOr use individual PG variables: PGHOST, PGPORT, , PGUSER, PGPASSWORD.
configPGHOSTOr use individual PG variables: , PGPORT, PGDATABASE, PGUSER, PGPASSWORD.
configPGPASSWORDOr use individual PG variables: PGHOST, PGPORT, PGDATABASE, PGUSER, .
configPGPORTOr use individual PG variables: PGHOST, , PGDATABASE, PGUSER, PGPASSWORD.
configPGUSEROr use individual PG variables: PGHOST, PGPORT, PGDATABASE, , PGPASSWORD.
configSQLITE_PATH
configTEST_DATABASE_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// 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

9/9 tools missing one or more hints — inspect_schema (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); analyze_indexes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); explain_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 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

8/9 tool handlers declare input schemas (89%)

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

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 3 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/dmitriusan/mcp-db-analyzer)](https://m8ven.ai/mcp/dmitriusan/mcp-db-analyzer)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ef86b573134a356b1e8ed3d10401bd5ffd23abe1
code hash: 6f857c68bcc6e6c47b6eec1a7721aa11f14f476e060fe953bca68a69cdc1ccc9
verified: 6/12/2026, 10:23:50 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