Ext Ops Panel
Open dashboard
Comparison

Program Integrity Alliance vs NYC Property & Venue API

Program Integrity Alliance is an MCP server published by Program-Integrity-Alliance. Marketplaces we read that list it: 1 (Docker MCP Catalog). NYC Property & Venue API is an MCP server published by MatchupLabs. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceProgram Integrity AllianceNYC Property & Venue API
Docker MCP Catalog Listed
Version: sha256:7b4f383fd466
Forks (GitHub): 1
Pulls (Docker Hub): 13 268
Stars (Docker Hub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (npm): 127
Downloads/week (npm): 25
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 NYC Property & Venue API
FactProgram Integrity AllianceNYC Property & Venue API
Marketplaces that list it11
Stars (GitHub) (differs)4No figure on GitHub
Pulls (Docker Hub) (differs)13 268No figure on Docker Hub
Forks (GitHub) (differs)1No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/pia)On your machine (@matchuplabs/nyc-api-mcp)
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/matchup-labs/nycapi
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

Program Integrity Alliance

In its own words, on Docker MCP Catalog:

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

NYC Property & Venue API

In its own words, on Official MCP Registry:

NYC property intelligence, building violations, and restaurant/venue compliance via MCP.

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)

NYC Property & Venue API As a local MCP server: npm package

Claude Code
claude mcp add --env "NYC_API_KEY=<YOUR_NYC_API_KEY>" --transport stdio nyc-api -- npx -y @matchuplabs/nyc-api-mcp

Requires: NYC_API_KEY (secret)

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

Tools each declares

The marketplaces of NYC Property & Venue API 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 NYC Property & Venue API asks for

  • NYC_API_BASE_URL
  • NYC_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: NYC Property & Venue API · 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