Ext Ops Panel
Open dashboard
Comparison

PgVouch vs dryrun

PgVouch is an MCP server published by Shubh-Sgr. Marketplaces we read that list it: 1 (Official MCP Registry). dryrun is an MCP server published by boringSQL. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplacePgVouchdryrun
Official MCP Registry Listed
Version: 0.4.4
Downloads/month (npm): 1 318
Downloads/week (npm): 49
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.19.1
Downloads/month (npm): 5 325
Downloads/week (npm): 472
Forks (GitHub): 4
Stars (GitHub): 36
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

PgVouch vs dryrun
FactPgVouchdryrun
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)36 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (pgvouch)On your machine (@boringsql/dryrun)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 2Not published
LicenceNot statedNot stated
Repository (differs)github.com/shubh-sgr/pgvouchgithub.com/boringsql/dryrun
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

PgVouch

In its own words, on Official MCP Registry:

Safe PostgreSQL migrations: schema drift, lock analysis, safe rewrites, data checksums. Read-only.

dryrun

In its own words, on Official MCP Registry:

PostgreSQL schema intelligence from a committed snapshot. No connection, no credentials.

How to run each

PgVouch As a local MCP server: npm package

Claude Code
claude mcp add --env "SOURCE_DATABASE_URL=<YOUR_SOURCE_DATABASE_URL>" --env "TARGET_DATABASE_URL=<YOUR_TARGET_DATABASE_URL>" --transport stdio pgvouch -- npx -y pgvouch mcp

Requires: SOURCE_DATABASE_URL (secret), TARGET_DATABASE_URL (secret)

dryrun As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio dryrun -- npx -y @boringsql/dryrun mcp-serve

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

The marketplaces of dryrun publish no settings it asks for, so we do not compare settings.

What it can do: PgVouch · What it can do: dryrun · 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