Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

dbmole

NPM · DBMOLE-MCP

PostgreSQL and MySQL with connections managed at runtime by the agent, SSH tunnels, readonly.

Available components

+4 this week 66 Trust /100

Last scanned (3 hours ago)

Scores higher than 34% of npm servers

Category Databases

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 41 of 125 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 701 tokens (~77/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 28% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_connection" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/dbmole-mcp@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 125 packages
Packages resolved 125
Stale 41
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~701 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_connection ~158

Add a named postgres/mysql connection. scope "global" (default) saves it to the user store; "project" saves it to .dbmole.json in the project root. Supports an optional ssh tunnel and a readonly flag. Optional ssl: true or { rejectUnauthorized, ca } (ca = PEM or file path).

NameTypeReqDescription
databasestring––
hoststringyes–
namestringyes–
passwordstring––
portinteger––
queryTimeoutMsinteger––
readonlyboolean––
scopestring––
sshobject––
ssl–––
typestringyes–
userstringyes–

No output schema declared.

No examples provided.

describe_table ~86

Describe a table or view: columns (type, nullable, default), primary key, indexes and foreign keys.

NameTypeReqDescription
connectionstringyesconnection name, see list_connections
databasestring––
schemastring–postgres schema, defaults to public
tablestringyestable name; may be qualified: schema.table (postgres), db.table (mysql)

No output schema declared.

No examples provided.

execute_sql ~106

Execute a single SQL statement on a named connection. SELECT returns columns/rows; DML returns rowCount (and lastInsertId for mysql). Use positional params: $1.. for postgres, ? for mysql.

NameTypeReqDescription
connectionstringyesconnection name, see list_connections
databasestring–database to run against; defaults to the connection default
paramsarray–positional query parameters
rowLimitinteger––
sqlstringyes–

No output schema declared.

No examples provided.

list_connections ~52

List database connections with the layer each comes from: project (.dbmole.json, found by walking up from the project dir) or global (user store). Also shows invalid entries and broken files. Secrets are omitted.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_databases ~42

List databases on a connection with size in bytes. Hides postgres template databases and mysql system schemas.

NameTypeReqDescription
connectionstringyesconnection name, see list_connections

No output schema declared.

No examples provided.

list_tables ~67

List tables and views (type: table | view) with approximate row counts. For postgres, optionally filter by schema; for mysql, schema is the database.

NameTypeReqDescription
connectionstringyesconnection name, see list_connections
databasestring––
schemastring––

No output schema declared.

No examples provided.

remove_connection ~39

Remove a connection by name from the layer it lives in (invalid entries too) and drop its cached pools/tunnel.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

test_connection ~38

Verify a connection works end to end (including ssh tunnel if configured). Reports server version and connect+query latency.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

update_connection ~113

Patch a connection by name in the layer it lives in (project or global). Set a field to null to remove it (e.g. "ssh": null); an ssh object is merged field by field, e.g. { "ssh": { "hostKey": "SHA256:..." } }. queryTimeoutMs sets the per-statement timeout (null restores the 60 s default). ssl is replaced as a whole, not merged like ssh.

NameTypeReqDescription
namestringyes–
patchobjectyes–

No output schema declared.

No examples provided.

Install

How do I install the dbmole MCP server?

dbmole runs locally as an npm package, launched with npx -y dbmole-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · dbmole-mcp

# add to Claude Code
claude mcp add ed-smartass-dbmole-mcp -- npx -y dbmole-mcp
Common questions

What is the dbmole MCP server?

dbmole is an MCP server listed in the public MCP registry as io.github.ed-smartass/dbmole-mcp. PostgreSQL and MySQL with connections managed at runtime by the agent, SSH tunnels, readonly. This page covers its npm package (dbmole-mcp).

Is the dbmole MCP server safe to use?

dbmole scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the dbmole MCP server expose?

dbmole exposes 9 tools: list_connections, add_connection, update_connection, remove_connection, test_connection, and 4 more. Their descriptions and schemas cost roughly 701 tokens of context every time the server is loaded.

Is the dbmole MCP server still maintained?

dbmole is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the dbmole MCP server under?

dbmole declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.