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.
223
29 Tools
Version 4.43 or later needs to be installed to add the server automatically
Tools
Name | Description |
---|---|
baseline_population_get | Baseline population data sourced and maintained by UNFPA (UN Population Fund). See the more detailed technical <a href="https://hdx-hapi.readthedocs.io/en/latest/data_usage_guides/population_and_socio-economy/#baseline-population">HDX HAPI documentation</a>, and the <a href="https://data.humdata.org/organization/unfpa">UNFPA on HDX</a>. **Query Parameters:** - **app_identifier** (Required): base64 encoded application name and email, as in `base64("app_name:email")`. This value can also be passed in the `X-HDX-HAPI-APP-IDENTIFIER` header. See the *encoded_app_identifier* endpoint. - **gender**: Filter the response by the gender, available values are described <a href="https://hdx-hapi.readthedocs.io/en/latest/data_usage_guides/enums/#gender">here.</a> - **age_range**: Filter the response by the age range. These are expressed as [start age]-[end age], or [start age]+ for an age range starting at [start age] or above. The end age is assumed to be inclusive, though that is not always explicit in the source data. - **population_min**: Filter the response by a lower bound for the population. - **population_max**: Filter the response by a upper bound for the population. - **has_hrp**: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan. - **in_gho**: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the <a href="https://humanitarianaction.info/">Global Humanitarian Overview</a>. - **start_date**: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00 - **end_date**: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59 - **location_code**: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names. - **location_name**: Filter the response by a location (typically a country). The location names are based on the "short name" from the <a href="https://unstats.un.org/unsd/methodology/m49/#fn2">UN M49 Standard</a>. Use the metadata_location_get tool to get available location codes and names. - **admin1_code**: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the <a href="https://data.humdata.org/dashboards/cod?">Common Operational Datasets</a>. Use the metadata_admin1_get tool to get available admin1 codes and names. - **admin1_name**: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the <a href="https://data.humdata.org/dashboards/cod?">Common Operational Datasets</a> or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names. - **admin2_code**: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the <a href="https://data.humdata.org/dashboards/cod?">Common Operational Datasets</a>. Use the metadata_admin2_get tool to get available admin2 codes and names. - **admin2_name**: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the <a href="https://data.humdata.org/dashboards/cod?">Common Operational Datasets</a> or those provided in the original data source. Use the metadata_admin2_get tool to get available admin2 codes and names. - **admin_level**: Filter the response by admin level. - **output_format**: No description. - **limit**: Maximum number of records to return. The system will not return more than 10,000 records. - **offset**: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate. **Responses:** - **200** (Success): Successful Response - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "data": [ { "location_code": "string", "location_name": "string", "admin1_code": "unknown_type", "population": 1, "admin_level": 1, "min_age": "unknown_type", "resource_hdx_id": "string", "admin2_name": "unknown_type", "max_age": "unknown_type", "reference_period_end": "unknown_type", "admin2_code": "unknown_type", "gender": "f", "age_range": "string", "reference_period_start": "unknown_type", "admin1_name": "unknown_type" } ] } ``` - **400**: Bad Request - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "detail": "string" } ``` - **422**: Validation Error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "detail": [ { "loc": [ "unknown_type" ], "msg": "string", "type": "string" } ] } ``` - **500**: Internal Server Error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "error_sample_list": [ "unknown" ], "error": "string" } ``` |
Manual installation
You can install the MCP server using:
Installation for