Program Integrity Alliance vs Google Ads Transparency Scraper & Monitor
Program Integrity Alliance is an MCP server published by Program-Integrity-Alliance. Marketplaces we read that list it: 1 (Docker MCP Catalog). Google Ads Transparency Scraper & Monitor is an MCP server published by akhilrajesh213. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  Google Ads Transparency Scraper & Monitor |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7b4f383fd466 Forks (GitHub): 1 Pulls (Docker Hub): 14 003 Stars (Docker Hub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.13 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 | Google Ads Transparency Scraper & Monitor |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 14 003 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | On your machine (mcp/pia) | Remote server (akhil-rajesh--google-ads-transparency-scraper.apify.actor/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 (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-27 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 8 h ago, requires authentication |
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.
Google Ads Transparency Scraper & Monitor
Google Ads Transparency Center for AI agents: brands' ads, ad copy, political ad spend, removed ads.
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)
Google Ads Transparency Scraper & Monitor As a remote MCP server
claude mcp add --transport http google-ads-transparency https://akhil-rajesh--google-ads-transparency-scraper.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Google Ads Transparency Scraper & Monitor has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Google Ads Transparency Scraper & Monitor publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Google Ads Transparency Scraper & Monitor publish no settings it asks for, so we do not compare settings.
What it can do: Program Integrity Alliance · What it can do: Google Ads Transparency Scraper & Monitor · 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.