Ext Ops Panel
Open dashboard
Comparison

Program Integrity Alliance vs Arcgis Peterborough

Program Integrity Alliance is an MCP server published by Program-Integrity-Alliance. Marketplaces we read that list it: 1 (Docker MCP Catalog). Arcgis Peterborough is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 AllianceArcgis Peterborough
Docker MCP Catalog Listed
Version: sha256:7b4f383fd466
Forks (GitHub): 1
Pulls (Docker Hub): 13 958
Stars (Docker Hub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
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 Arcgis Peterborough
FactProgram Integrity AllianceArcgis Peterborough
Marketplaces that list it11
Stars (GitHub) (differs)4 (better)0 (worse)
Pulls (Docker Hub) (differs)13 958No figure on Docker Hub
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-30
Where it runs (differs)On your machine (mcp/pia)Remote server (gateway.pipeworx.io/arcgis-peterborough/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/program-integrity-alliance/pia-mcp-localgithub.com/pipeworx-io/mcp-arcgis-peterborough
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 2 days ago returned HTTP 200

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.

Arcgis Peterborough

In its own words, on Official MCP Registry:

City of Peterborough GIS — Peterborough, Ontario (Canada) open geospatial data (ArcGIS).

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)

Arcgis Peterborough As a remote MCP server

Claude Code
claude mcp add --transport http arcgis-peterborough https://gateway.pipeworx.io/arcgis-peterborough/mcp

Requires: PIPEWORX_API_KEY (secret)

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

Only Arcgis Peterborough has a remote endpoint we check. How we check endpoints

Tools each declares

Only Program Integrity Alliance has

  • pia_oversight_recommendations
  • pia_search

Only Arcgis Peterborough has

  • ai_visibility_check
  • archive_compare
  • archive_evidence
  • ask_pipeworx
  • ask_pipeworx_beta
  • ask_pipeworx_grounded
  • bet_research
  • classify_row
  • company_facts
  • company_register_search
  • compare_entities
  • deep_research
Show the remaining 33
  • discover_tools
  • entity_profile
  • forget
  • generate_llms_txt
  • kalshi_weather_edge
  • layer_info
  • list_subscriptions
  • pipeworx_feedback
  • pipeworx_trending
  • polymarket_arbitrage
  • polymarket_edge_tracker
  • polymarket_edges
  • polymarket_fill_risk
  • polymarket_kalshi_spread
  • prediction_calibration
  • query_layer
  • recall
  • recent_alerts
  • recent_changes
  • release_calendar_markets
  • remember
  • research_row
  • resolution_audit
  • resolution_diff
  • resolve_entity
  • scan_competitor_ai_presence
  • scan_dependency
  • search_datasets
  • search_within
  • subscribe
  • suggest_questions
  • unsubscribe
  • validate_claim

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Arcgis Peterborough as of 2026-10-27). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Program Integrity Alliance asks for

  • PIA_API_KEY (secret)

Only Arcgis Peterborough asks for

  • PIPEWORX_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: Arcgis Peterborough · 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