Ext Ops Panel
Open dashboard
Comparison

SQLite (Archived) vs PostgreSQL Performance (read-only)

SQLite (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). PostgreSQL Performance (read-only) is an MCP server published by gouranshul. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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
MarketplaceSQLite (Archived)PostgreSQL Performance (read-only)
Docker MCP Catalog Listed
Version: sha256:efbc05ccace1
Forks (GitHub): 11 780
Pulls (Docker Hub): 72 786
Stars (Docker Hub): 16
Stars (GitHub): 91 180
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
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

SQLite (Archived) vs PostgreSQL Performance (read-only)
FactSQLite (Archived)PostgreSQL Performance (read-only)
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)91 180 (better)0 (worse)
Pulls (Docker Hub) (differs)72 786No figure on Docker Hub
Forks (GitHub) (differs)11 780 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sqlite)On your machine (ghcr.io/gouranshul/pg-perf-mcp:0.1.0)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks for (differs)Not published4, secrets among them: 2
Parts of the bundle (differs)Not a bundle1
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/gouranshul/pg-perf-mcp
Changes in the last 7 days (differs)02
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

SQLite (Archived)

In its own words, on Docker MCP Catalog:

Database interaction and business intelligence capabilities.

PostgreSQL Performance (read-only)

In its own words, on Official MCP Registry:

Read-only PostgreSQL performance diagnostics: slow queries, EXPLAIN, index advice, locks, functions

How to run each

SQLite (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio sqlite -- docker run -i --rm mcp/sqlite

PostgreSQL Performance (read-only) As a Claude Code plugin

Claude Code
/plugin marketplace add gouranshul/pg-perf-mcp
/plugin install pg-perf@pg-perf-mcp

Requires: MCP_API_KEY (secret), PGPERF_DB_PASSWORD (secret), PGPERF_DB_URL, PGPERF_DB_USER

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

Tools each declares

The marketplaces of PostgreSQL Performance (read-only) publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of SQLite (Archived) publish no settings it asks for, so we do not compare settings.

What it can do: SQLite (Archived) · What it can do: PostgreSQL Performance (read-only) · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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