Ext Ops Panel
Open dashboard
Comparison

io.github.Fashad-Ahmed/universal-db-mcp vs io.github.rzlco666/strut-stack-sql

io.github.Fashad-Ahmed/universal-db-mcp is an MCP server published by Fashad-Ahmed. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.rzlco666/strut-stack-sql is an MCP server published by rzlco666. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplaceio.github.Fashad-Ahmed/universal-db-mcpio.github.rzlco666/strut-stack-sql
Official MCP Registry Listed
Version: 1.1.2
Downloads/month (PyPI): 114
Downloads/week (PyPI): 25
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.4
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

io.github.Fashad-Ahmed/universal-db-mcp vs io.github.rzlco666/strut-stack-sql
Factio.github.Fashad-Ahmed/universal-db-mcpio.github.rzlco666/strut-stack-sql
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (universal-db-mcp)On your machine (https://github.com/rzlco666/strut-stack-sql/releases/download/v1.0.4/strut-stack-sql-linux-x64.mcpb)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)6, secrets among them: 21, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/fashad-ahmed/universal-mcpgithub.com/rzlco666/strut-stack-sql
Changes in the last 7 days00
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

io.github.Fashad-Ahmed/universal-db-mcp

In its own words, on Official MCP Registry:

Security-first MCP server for PostgreSQL, SQLite, MySQL, DuckDB with SQL injection prevention.

io.github.rzlco666/strut-stack-sql

In its own words, on Official MCP Registry:

Token-efficient MCP server for MySQL, PostgreSQL, and SQLite

How to run each

io.github.Fashad-Ahmed/universal-db-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --env "MYSQL_URI=<YOUR_MYSQL_URI>" --env "POSTGRES_URI=<YOUR_POSTGRES_URI>" --transport stdio universal-db-mcp -- uvx universal-db-mcp

Requires: MYSQL_URI (secret), POSTGRES_URI (secret)

io.github.rzlco666/strut-stack-sql

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: DATABASE_URL (secret)

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 io.github.Fashad-Ahmed/universal-db-mcp asks for

  • ALLOW_DESTRUCTIVE
  • DUCKDB_PATH
  • MAX_RESULT_ROWS
  • MYSQL_URI (secret)
  • POSTGRES_URI (secret)
  • SQLITE_PATH

Only io.github.rzlco666/strut-stack-sql asks for

  • DATABASE_URL (secret)

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

What it can do: io.github.Fashad-Ahmed/universal-db-mcp · What it can do: io.github.rzlco666/strut-stack-sql · 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