Ext Ops Panel
Open dashboard
Comparison

Program Integrity Alliance vs H/M Content Credentials Evidence Verifier

Program Integrity Alliance is an MCP server published by Program-Integrity-Alliance. Marketplaces we read that list it: 1 (Docker MCP Catalog). H/M Content Credentials Evidence Verifier is an MCP server published by hogarmas.net. 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

Where each is published
MarketplaceProgram Integrity AllianceH/M Content Credentials Evidence Verifier
Docker MCP Catalog Listed
Version: sha256:7b4f383fd466
Forks (GitHub): 1
Pulls (Docker Hub): 13 289
Stars (Docker Hub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.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

Program Integrity Alliance vs H/M Content Credentials Evidence Verifier
FactProgram Integrity AllianceH/M Content Credentials Evidence Verifier
Marketplaces that list it11
Stars (GitHub) (differs)4No figure on GitHub
Pulls (Docker Hub) (differs)13 289No figure on Docker Hub
Forks (GitHub) (differs)1No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/pia)Remote server (agents.hogarmas.net/mcp/content-credentials)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/program-integrity-alliance/pia-mcp-localNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days 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

In its own words, on Docker MCP Catalog:

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

H/M Content Credentials Evidence Verifier

In its own words, on Official MCP Registry:

Free C2PA 2.4 triage and reproducible official trust snapshot. No media, keys, or payment.

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)

H/M Content Credentials Evidence Verifier As a remote MCP server

Claude Code
claude mcp add --transport http content-credentials https://agents.hogarmas.net/mcp/content-credentials

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

Only H/M Content Credentials Evidence Verifier has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of H/M Content Credentials Evidence Verifier publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of H/M Content Credentials Evidence Verifier publish no settings it asks for, so we do not compare settings.

What it can do: Program Integrity Alliance · What it can do: H/M Content Credentials Evidence Verifier · 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