Querybridge MCP Server
querybridge-mcp
npm
v0.13.0
Source verified
Published by mahmoudhassanmustafa — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server connecting Claude Code with MySQL — supports SSH tunnels and multiple databases
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Reads a sensitive credential path or dumps the environment (dist/server/cli.js)MTC-SRC-006
In the server's implementation (`dist/server/cli.js:135`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: vate key path", "~/.ssh/id_rsa")); const passphrase = await ask(rl, " Key passphrase (optional)");
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/server/cli.js
Tools 40
Each tool and what it can reach — statically extracted from the published source.
execute_queryreads sensitive datainnodb_statusreads sensitive datacolumn_statsno sensitive capabilitycompare_schema_fileno sensitive capabilitycompare_schemasno sensitive capabilitycurrent_locksno sensitive capabilitydescribe_tableno sensitive capabilitydescribe_viewno sensitive capabilityexplain_queryno sensitive capabilitygenerate_erdno sensitive capability
Show 30 more tools ↓
generate_migrationno sensitive capabilityget_charset_collationno sensitive capabilityget_ddlno sensitive capabilityget_event_ddlno sensitive capabilityget_foreign_keysno sensitive capabilityget_indexesno sensitive capabilityget_routine_ddlno sensitive capabilityget_table_statsno sensitive capabilityget_trigger_ddlno sensitive capabilityget_unused_indexesno sensitive capabilityget_view_ddlno sensitive capabilitykill_queryno sensitive capabilitylist_connectionsno sensitive capabilitylist_databasesno sensitive capabilitylist_eventsno sensitive capabilitylist_processesno sensitive capabilitylist_routinesno sensitive capabilitylist_tablesno sensitive capabilitylist_triggersno sensitive capabilitylist_viewsno sensitive capabilityreconnectno sensitive capabilitysample_datano sensitive capabilitysearch_columnsno sensitive capabilityserver_infono sensitive capabilityshow_statusno sensitive capabilityshow_variablesno sensitive capabilityslow_queriesno sensitive capabilitystreaming_queryno sensitive capabilitytraverse_fkno sensitive capabilityuse_databaseno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (40 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.13.0 latest |
A 97/100 | 1 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan querybridge-mcp --onlineMore in Databases
Security scan results for the A5sql MCP server.
Expose AgentsKit tools as an MCP server — use them from Claude Desktop, Cursor, Windsurf, or any MCP host.
MCP server for Aiven cloud data platform - manage PostgreSQL, Kafka, and other services
MCP Server for All-Inkl.com hosting via KAS API
Structured aquarium, marine, terrarium and paludarium data for AI agents.
MCP server that gives your AI agent real vehicle data — specs, representative images, federal recalls, owner complaints, service bulletins, defect investigations, and OBD-II DTC reference — from the CarVector API.