Ext Ops Panel
Open dashboard
Comparison

Program Integrity Alliance vs io.github.cyanheads/openfda-mcp-server

Program Integrity Alliance is an MCP server published by Program-Integrity-Alliance. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.cyanheads/openfda-mcp-server is an MCP server published by cyanheads. 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 Allianceio.github.cyanheads/openfda-mcp-server
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: 0.8.1
Downloads/month (npm): 2 108
Downloads/week (npm): 264
Forks (GitHub): 2
Stars (GitHub): 4
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 io.github.cyanheads/openfda-mcp-server
FactProgram Integrity Allianceio.github.cyanheads/openfda-mcp-server
Marketplaces that list it11
Stars (GitHub)44
Pulls (Docker Hub) (differs)13 290No figure on Docker Hub
Forks (GitHub) (differs)1 (worse)2 (better)
Last release (differs)Not published2026-10-13
Where it runs (differs)On your machine (mcp/pia)Remote server (openfda.caseyjhand.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 115, secrets among them: 0
Licence (differs)MITNot stated
Repository (differs)github.com/program-integrity-alliance/pia-mcp-localgithub.com/cyanheads/openfda-mcp-server
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 12 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

In its own words, on Docker MCP Catalog:

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

io.github.cyanheads/openfda-mcp-server

In its own words, on Official MCP Registry:

Query FDA data on drugs, food, devices, and recalls via openFDA. STDIO or Streamable HTTP.

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)

io.github.cyanheads/openfda-mcp-server As a remote MCP server

Claude Code
claude mcp add --transport http openfda-mcp-server https://openfda.caseyjhand.com/mcp

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

Only io.github.cyanheads/openfda-mcp-server has a remote endpoint we check. How we check endpoints

Tools each declares

Only Program Integrity Alliance has

  • pia_oversight_recommendations
  • pia_search

Only io.github.cyanheads/openfda-mcp-server has

  • openfda_count_values
  • openfda_dataframe_describe
  • openfda_dataframe_query
  • openfda_describe_fields
  • openfda_drug_profile
  • openfda_get_drug_label
  • openfda_lookup_ndc
  • openfda_search_adverse_events
  • openfda_search_animal_events
  • openfda_search_device_clearances
  • openfda_search_drug_approvals
  • openfda_search_drug_shortages
Show the remaining 2
  • openfda_search_recalls
  • openfda_search_tobacco_reports

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.cyanheads/openfda-mcp-server as of 2026-10-17). 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 io.github.cyanheads/openfda-mcp-server asks for

  • CANVAS_PROVIDER_TYPE
  • MCP_AUTH_MODE
  • MCP_HTTP_ENDPOINT_PATH
  • MCP_HTTP_HOST
  • MCP_HTTP_PORT
  • MCP_LOG_LEVEL
  • MCP_TRANSPORT_TYPE
  • OPENFDA_API_KEY
  • OPENFDA_DATAFRAME_DROP_ENABLED
  • OPENFDA_MIRROR_BASE_URL
  • OPENFDA_MIRROR_ENABLED
  • OPENFDA_MIRROR_FALLBACK_LIVE
Show the remaining 3
  • OPENFDA_MIRROR_PATH
  • OPENFDA_MIRROR_REFRESH_CRON
  • OPENFDA_MIRROR_REFRESH_TIMEOUT_MS

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: io.github.cyanheads/openfda-mcp-server · 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