Ext Ops Panel
Open dashboard
Comparison

ai.haymon/dbmcp vs io.github.rosch100/mcp-encrypted-sqlite

ai.haymon/dbmcp is an MCP server published by haymon.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.rosch100/mcp-encrypted-sqlite is an MCP server published by rosch100. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceai.haymon/dbmcpio.github.rosch100/mcp-encrypted-sqlite
Official MCP Registry Listed
Version: 0.15.2
Forks (GitHub): 8
Stars (GitHub): 32
Not marked · First seen
Listed
Version: 0.4.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

ai.haymon/dbmcp vs io.github.rosch100/mcp-encrypted-sqlite
Factai.haymon/dbmcpio.github.rosch100/mcp-encrypted-sqlite
Marketplaces that list it11
Stars (GitHub) (differs)32 (better)0 (worse)
Forks (GitHub) (differs)8 (better)0 (worse)
Last release (differs)2026-10-26Not published
Where it runs (differs)On your machine (ghcr.io/haymon-ai/dbmcp:0.15.2)On your machine (ghcr.io/rosch100/mcp-encrypted-sqlite:0.4.1)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)5, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/haymon-ai/dbmcpgithub.com/rosch100/mcp-encrypted-sqlite
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

ai.haymon/dbmcp

In its own words, on Official MCP Registry:

Database MCP server for MySQL, MariaDB, PostgreSQL & SQLite with PII redaction and write-prevention

io.github.rosch100/mcp-encrypted-sqlite

In its own words, on Official MCP Registry:

MCP server for encrypted SQLite databases (SQLCipher 4) - Works with MoneyMoney, KeePass and more

How to run each

ai.haymon/dbmcp As a local MCP server: Docker image

Claude Code
claude mcp add --env "HTTP_AUTH_TOKEN=<YOUR_HTTP_AUTH_TOKEN>" --transport stdio dbmcp -- docker run -i --rm -e HTTP_AUTH_TOKEN ghcr.io/haymon-ai/dbmcp:0.15.2 stdio

Requires: HTTP_AUTH_TOKEN (secret)

io.github.rosch100/mcp-encrypted-sqlite As a local MCP server: Docker image

Claude Code
claude mcp add --env "DB_PASSPHRASE=<YOUR_DB_PASSPHRASE>" --env "DB_PATH=<YOUR_DB_PATH>" --transport stdio mcp-encrypted-sqlite -- docker run -i --rm -e DB_PASSPHRASE -e DB_PATH ghcr.io/rosch100/mcp-encrypted-sqlite:0.4.1

Requires: DB_PASSPHRASE (secret), DB_PATH

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only ai.haymon/dbmcp asks for

  • HTTP_ALLOWED_HOSTS
  • HTTP_ALLOWED_ORIGINS
  • HTTP_AUTH_TOKEN (secret)
  • HTTP_HOST
  • HTTP_PORT

Only io.github.rosch100/mcp-encrypted-sqlite asks for

  • DB_PASSPHRASE (secret)
  • DB_PATH

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: ai.haymon/dbmcp · What it can do: io.github.rosch100/mcp-encrypted-sqlite · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built