Ext Ops Panel
Open dashboard
Comparison

Program Integrity Alliance vs Vivory Korea Data Gateway

Vivory Korea Data Gateway is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.

Program Integrity Alliance is an MCP server published by Program-Integrity-Alliance. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vivory Korea Data Gateway is an MCP server published by jayjodev. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceProgram Integrity AllianceVivory Korea Data Gateway
Docker MCP Catalog Listed
Version: sha256:7b4f383fd466
Forks (GitHub): 1
Pulls (Docker Hub): 13 772
Stars (Docker Hub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Removed on 2026-10-23
Version: 0.6.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

Program Integrity Alliance vs Vivory Korea Data Gateway
FactProgram Integrity AllianceVivory Korea Data Gatewayno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)40
Pulls (Docker Hub) (differs)13 772No figure on Docker Hub
Forks (GitHub) (differs)10
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/pia)On your machine (vivory-mcp-korea)
Transportstdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/program-integrity-alliance/pia-mcp-localgithub.com/jayjodev/vivory-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. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of Vivory Korea Data Gateway

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

Its card, with similar plugins by marketplace

What each says it does

Program Integrity Alliance

In its own words, on Docker MCP Catalog:

An MCP server to help make U.S. Government open datasets AI-friendly.

Vivory Korea Data Gateway

In its own words, on Official MCP Registry:

DEPRECATED v0.6.0 — migrate to vivory-mcp-verification (Korean verdict tools included).

How to run each

Program Integrity Alliance As a local MCP server: Docker image

Claude Code
claude mcp add --env "PIA_API_KEY=<YOUR_PIA_API_KEY>" --transport stdio pia -- docker run -i --rm -e PIA_API_KEY mcp/pia

Requires: PIA_API_KEY (secret)

Vivory Korea Data Gateway

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

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

Tools each declares

The marketplaces of Vivory Korea Data Gateway publish no list of tools, so we do not compare tools.

Settings each asks for

Only Program Integrity Alliance asks for

  • PIA_API_KEY (secret)

Only Vivory Korea Data Gateway asks for

  • VIVORY_API_BASE
  • VIVORY_API_KEY (secret)

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

What it can do: Program Integrity Alliance · What it can do: Vivory Korea Data Gateway · 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. 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