PostgreSQL (hardened, read-only) vs Postgres (read-only)
PostgreSQL (hardened, read-only) is an MCP server published by Eszetael. Marketplaces we read that list it: 1 (Official MCP Registry). Postgres (read-only) is an MCP server published by contextflo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
| Marketplace |  PostgreSQL (hardened, read-only) |  Postgres (read-only) |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.10 Downloads/month (npm): 477 Downloads/week (npm): 94 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 0.1.4 Downloads/month (npm): 990 Downloads/week (npm): 84 Forks (GitHub): 0 Stars (GitHub): 4 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
| Fact | PostgreSQL (hardened, read-only) | Postgres (read-only) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (worse) | 4 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (postgres-mcp-hardened) | On your machine (@contextflo/postgres-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/eszetael/postgres-mcp-hardened | github.com/contextflo/postgres-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
PostgreSQL (hardened, read-only)
Read-only PostgreSQL over MCP. Writes refused at the parsed SQL, plus a READ ONLY transaction.
Postgres (read-only)
Read-only Postgres: drop-in for the archived server-postgres, with schema context.
How to run each
PostgreSQL (hardened, read-only) As a local MCP server: npm package
claude mcp add --env "DATABASE_URL=<YOUR_DATABASE_URL>" --transport stdio postgres-mcp-hardened -- npx -y --stdio postgres-mcp-hardenedRequires: DATABASE_URL (secret)
Postgres (read-only) As a local MCP server: npm package
claude mcp add --env "DATABASE_URL=<YOUR_DATABASE_URL>" --transport stdio postgres-mcp -- npx -y @contextflo/postgres-mcpRequires: 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 PostgreSQL (hardened, read-only) asks for
MCP_ADDRMCP_ALLOW_TABLESMCP_AUDIT_LOGMCP_STATEMENT_TIMEOUT
Only Postgres (read-only) asks for
None
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: PostgreSQL (hardened, read-only) · What it can do: Postgres (read-only) · 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.