Program Integrity Alliance vs Source Claim Proof
Program Integrity Alliance is an MCP server published by Program-Integrity-Alliance. Marketplaces we read that list it: 1 (Docker MCP Catalog). Source Claim Proof is an MCP server published by source-claim-proof.mattskowronis.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  Program Integrity Alliance | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7b4f383fd466 Forks (GitHub): 1 Pulls (Docker Hub): 13 290 Stars (Docker Hub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | Program Integrity Alliance | Source Claim Proof |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 13 290 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/pia) | Remote server (source-claim-proof.mattskowronis.workers.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/program-integrity-alliance/pia-mcp-local | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 h ago |
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
An MCP server to help make U.S. Government open datasets AI-friendly.
Source Claim Proof
Verify whether a supplied public source currently supports one atomic factual claim.
How to run each
Program Integrity Alliance As a local MCP server: Docker image
claude mcp add --env "PIA_API_KEY=<YOUR_PIA_API_KEY>" --transport stdio pia -- docker run -i --rm -e PIA_API_KEY mcp/piaRequires: PIA_API_KEY (secret)
Source Claim Proof As a remote MCP server
claude mcp add --transport http verify-source-claim https://source-claim-proof.mattskowronis.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Source Claim Proof has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Source Claim Proof publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Source Claim Proof publish no settings it asks for, so we do not compare settings.
What it can do: Program Integrity Alliance · What it can do: Source Claim Proof · 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.