Humanitarian Data Exchange vs Usaspending
Humanitarian Data Exchange is an MCP server published by dividor. Marketplaces we read that list it: 1 (Docker MCP Catalog). Usaspending 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-10-18. 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 |  Humanitarian Data Exchange |  Usaspending |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:4fc4363ac407 Forks (GitHub): 3 Pulls (Docker Hub): 12 450 Stars (Docker Hub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.5 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
| Fact | Humanitarian Data Exchange | Usaspending |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 12 450 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/hdx) | Remote server (gateway.pipeworx.io/usaspending/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 29 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/dividor/hdx-mcp | github.com/pipeworx-io/mcp-usaspending |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 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
Humanitarian Data Exchange
HDX MCP Server provides access to humanitarian data through the Humanitarian Data Exchange (HDX) API - https://data.humdata.org/hapi. This server offers 33 specialized tools for retrieving humanitarian information including affected populations (refugees, IDPs, returnees), baseline demographics, food security indicators, conflict data, funding information, and operational presence across hundreds of countries and territories. See repository for instructions on getting a free HDX_APP_INDENTIFIER for access.
Usaspending
USAspending MCP — Federal spending data from USAspending.gov API
How to run each
Humanitarian Data Exchange As a local MCP server: Docker image
claude mcp add --env "HDX_APP_IDENTIFIER=<YOUR_HDX_APP_IDENTIFIER>" --transport stdio hdx -- docker run -i --rm -e HDX_APP_IDENTIFIER mcp/hdxRequires: HDX_APP_IDENTIFIER (secret)
Usaspending As a remote MCP server
claude mcp add --transport http usaspending https://gateway.pipeworx.io/usaspending/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Usaspending has a remote endpoint we check. How we check endpoints
Tools each declares
Only Humanitarian Data Exchange has
affected_people_humanitarian_needs_getaffected_people_idps_getaffected_people_refugees_getaffected_people_returnees_getbaseline_population_getclimate_rainfall_getcoordination_conflict_events_getcoordination_funding_getcoordination_national_risk_getcoordination_operational_presence_getfood_prices_getfood_security_get
Show the remaining 17
hdx_get_dataset_infohdx_search_locationshdx_server_infometadata_admin1_getmetadata_admin2_getmetadata_currency_getmetadata_data_availability_getmetadata_dataset_getmetadata_location_getmetadata_org_getmetadata_org_type_getmetadata_resource_getmetadata_sector_getmetadata_wfp_commodity_getmetadata_wfp_market_getpoverty_rate_getutil_version_get
Only Usaspending has
ai_visibility_checkarchive_comparearchive_evidenceask_pipeworxask_pipeworx_betaask_pipeworx_groundedbet_researchclassify_rowcompany_factscompany_register_searchcompare_entitiesdeep_research
Show the remaining 36
discover_toolsentity_profileforgetgenerate_llms_txtkalshi_weather_edgelist_subscriptionspipeworx_feedbackpipeworx_trendingpolymarket_arbitragepolymarket_edge_trackerpolymarket_edgespolymarket_fill_riskpolymarket_kalshi_spreadrecallrecent_alertsrecent_changesrelease_calendar_marketsrememberresearch_rowresolution_auditresolution_diffresolve_entityscan_competitor_ai_presencescan_dependencysearch_withinsubscribesuggest_questionsunsubscribeusa_award_searchusa_expiring_awardsusa_incumbent_profileusa_recipient_profileusa_spending_by_agencyusa_spending_by_categoryusa_spending_trendsvalidate_claim
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Usaspending as of 2026-10-15). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Usaspending publish no settings it asks for, so we do not compare settings.
What it can do: Humanitarian Data Exchange · What it can do: Usaspending · 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.