# dbmole (npm · dbmole-mcp)

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

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `dbmole-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/ed-smartass-dbmole-mcp/dbmole-mcp.md), [page](https://verifymcp.io/servers/ed-smartass-dbmole-mcp/dbmole-mcp)

## Channel facts

- Registry: `npm`
- Package: `dbmole-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 41 of 125 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 701 tokens (~77/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 28% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add ed-smartass-dbmole-mcp -- npx -y dbmole-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ed-smartass-dbmole-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dbmole-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ed-smartass-dbmole-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dbmole-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ed-smartass-dbmole-mcp -- npx -y dbmole-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ed-smartass-dbmole-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "dbmole-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ed-smartass-dbmole-mcp --command npx --arg -y --arg dbmole-mcp
```

### Hermes

```yaml
mcp_servers:
  ed-smartass-dbmole-mcp:
    command: "npx"
    args: ["-y", "dbmole-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ed-smartass-dbmole-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "dbmole-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ed-smartass-dbmole-mcp -t stdio -c npx -a -y dbmole-mcp
```

### Other

```json
{
  "mcpServers": {
    "ed-smartass-dbmole-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dbmole-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 66, +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.

### 2026-11-03 (score 65, +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.

### 2026-11-01 (score 64, +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.

### 2026-10-30 (score 63, +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.

### 2026-10-27 (score 62, +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.

### 2026-10-25 (score 61)

First indexed and scored.

## MCP tools (9)

### `list_connections` (~52 tokens)

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.

### `add_connection` (~158 tokens)

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).

Input parameters:

- `database` (string)
- `host` (string, required)
- `name` (string, required)
- `password` (string)
- `port` (integer)
- `queryTimeoutMs` (integer)
- `readonly` (boolean)
- `scope` (string)
- `ssh` (object)
- `ssl`
- `type` (string, required)
- `user` (string, required)

### `update_connection` (~113 tokens)

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.

Input parameters:

- `name` (string, required)
- `patch` (object, required)

### `remove_connection` (~39 tokens)

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

Input parameters:

- `name` (string, required)

### `test_connection` (~38 tokens)

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

Input parameters:

- `name` (string, required)

### `execute_sql` (~106 tokens)

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.

Input parameters:

- `connection` (string, required): connection name, see list_connections
- `database` (string): database to run against; defaults to the connection default
- `params` (array): positional query parameters
- `rowLimit` (integer)
- `sql` (string, required)

### `list_databases` (~42 tokens)

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

Input parameters:

- `connection` (string, required): connection name, see list_connections

### `list_tables` (~67 tokens)

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

Input parameters:

- `connection` (string, required): connection name, see list_connections
- `database` (string)
- `schema` (string)

### `describe_table` (~86 tokens)

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

Input parameters:

- `connection` (string, required): connection name, see list_connections
- `database` (string)
- `schema` (string): postgres schema, defaults to public
- `table` (string, required): table name; may be qualified: schema.table (postgres), db.table (mysql)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/ed-smartass-dbmole-mcp/dbmole-mcp#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 65
- 2026-11-03: 65
- 2026-11-02: 64
- 2026-11-01: 64
- 2026-10-31: 63
- 2026-10-30: 63
- 2026-10-29: 62
- 2026-10-28: 62
- 2026-10-27: 62
- 2026-10-26: 61
- 2026-10-25: 61

## 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.

## Links

- npm package: https://www.npmjs.com/package/dbmole-mcp
- Socket report: https://socket.dev/npm/package/dbmole-mcp
- Repository: https://github.com/ed-smartass/dbmole-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ed-smartass-dbmole-mcp/dbmole-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ed-smartass-dbmole-mcp/dbmole-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ed-smartass-dbmole-mcp/dbmole-mcp