who-gho-mcp-server
Server Details
WHO Global Health Observatory — 3,059 indicators across 194 member states.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- cyanheads/who-gho-mcp-server
- GitHub Stars
- 1
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.6/5 across 6 of 6 tools scored.
Each tool has a clearly distinct purpose: listing dimensions, dimension values, indicators, searching indicators, fetching indicator metadata, and querying data. There is no ambiguity or overlap between the six tools.
All tool names follow a consistent pattern: 'who_' prefix + verb_noun in snake_case (e.g., who_list_dimensions, who_query_indicator_data). No mixing of conventions.
With 6 tools, the server is well-scoped for a data query API. It covers discovery, metadata, and data retrieval without being bloated or too sparse.
The tool surface covers the full workflow: browse/search indicators, inspect metadata, list dimensions and values, and query data. No obvious gaps for a read-only API.
Available Tools
6 toolswho_get_indicator_metadataGet WHO GHO Indicator MetadataRead-onlyIdempotentInspect
Fetch metadata for one or more WHO GHO indicator codes: the full indicator name and the dimensions it supports (e.g. COUNTRY, REGION, SEX, YEAR, WORLDBANKINCOMEGROUP, AGEGROUP). Call this before querying data with who_query_indicator_data to confirm which filter dimensions are valid for a given indicator. Accepts up to 10 codes per call. Codes with no metadata are reported in the notFound array rather than causing an error.
| Name | Required | Description | Default |
|---|---|---|---|
| indicator_codes | Yes | One to ten indicator codes, e.g. ["WHOSIS_000001", "MDG_0000000026"]. |
Output Schema
| Name | Required | Description |
|---|---|---|
| notFound | Yes | Indicator codes that returned no metadata — they may not exist in the GHO catalog. |
| indicators | Yes | Metadata for each code that returned results. |
who_list_dimensionsList GHO Dimension TypesRead-onlyIdempotentInspect
List all dimension type codes and human-readable titles available in the WHO Global Health Observatory API. Use this to discover valid dimension codes before calling who_list_dimension_values. Common dimensions include COUNTRY, REGION, SEX, WORLDBANKINCOMEGROUP, and AGEGROUP, but many additional types exist — this tool exposes them all.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| dimensions | Yes | All available dimension types in the GHO catalog. |
who_list_dimension_valuesList GHO Dimension ValuesRead-onlyIdempotentInspect
List valid codes and labels for a WHO GHO dimension type such as COUNTRY, REGION, SEX, WORLDBANKINCOMEGROUP, or AGEGROUP. Use this to discover valid filter values before calling who_query_indicator_data, or to confirm the correct ISO code for a country. Use who_list_dimensions to discover all available dimension type codes.
| Name | Required | Description | Default |
|---|---|---|---|
| dimension | Yes | Dimension type code. Use who_list_dimensions to discover all available codes. Common values: COUNTRY, REGION, SEX, WORLDBANKINCOMEGROUP, AGEGROUP. |
Output Schema
| Name | Required | Description |
|---|---|---|
| values | Yes | Valid values for this dimension type. |
| dimension | Yes | The requested dimension type code. |
who_list_indicatorsList WHO GHO IndicatorsRead-onlyIdempotentInspect
Browse the WHO Global Health Observatory indicator catalog with pagination. Use when you want to explore indicators without a keyword, or to page through the full catalog. Use who_search_indicators when you have a keyword to narrow the results.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of indicators to return per page. Default 50, max 500. | |
| offset | No | Zero-based offset for pagination. Default 0. |
Output Schema
| Name | Required | Description |
|---|---|---|
| hasMore | Yes | True when more indicators exist beyond the current page. |
| pageInfo | Yes | Human-readable page position, e.g. "offset 0, showing 50 of 3059". Use to construct the next offset. |
| indicators | Yes | Indicators for the requested page. |
| totalCount | Yes | Total number of indicators in the GHO catalog. |
who_query_indicator_dataQuery WHO GHO Indicator DataRead-onlyIdempotentInspect
Query data rows for a single WHO GHO indicator with optional spatial, temporal, and dimension filters. Returns rows with numeric values, uncertainty intervals (Low/High), and spatial/time metadata. This is the primary data-fetching tool in the find-then-query workflow: use who_search_indicators to find the indicator code, optionally call who_get_indicator_metadata to confirm which filter dimensions are valid, then call this tool. Spatial filters are mutually exclusive per call: provide only one of country_codes, region_codes, or income_group_codes — mixing them triggers an error. Omitting all spatial filters returns all geographies (may be large; use limit to cap). The sex filter only applies when the indicator uses SEX as its first cross-cutting dimension — if not, the filter returns empty rows; check who_get_indicator_metadata first if uncertain.
| Name | Required | Description | Default |
|---|---|---|---|
| sex | No | Filter on sex dimension: SEX_BTSX (both sexes), SEX_FMLE (female), SEX_MLE (male). Only applies when the indicator uses SEX as its first cross-cutting dimension. | |
| limit | No | Maximum number of data rows to return. Default 200, max 1000. | |
| year_to | No | End year (inclusive) for the time range filter, e.g. 2023. | |
| year_from | No | Start year (inclusive) for the time range filter, e.g. 2015. | |
| dim1_value | No | Value filter for indicators whose first cross-cutting dimension is not SEX (e.g. an AGEGROUP code like "YEARS05-14"). Ignored when sex is also provided. | |
| region_codes | No | WHO region codes to filter on, e.g. ["AFR","EUR","AMR","EMR","SEAR","WPR"]. Returns the aggregate row for each named WHO region — not per-country rows within it. To get country-level data for a region, use who_list_dimension_values with dimension="COUNTRY" and filter by parentCode to retrieve the ISO codes for countries in that region, then pass those to country_codes. Use who_list_dimension_values with dimension="REGION" to see all valid region codes. Mutually exclusive with country_codes and income_group_codes. | |
| country_codes | No | ISO 3166-1 alpha-3 country codes to filter on, e.g. ["JPN","USA","BRA"]. Mutually exclusive with region_codes and income_group_codes. | |
| indicator_code | Yes | Indicator code to query, e.g. "WHOSIS_000001". Use who_search_indicators to find codes. | |
| income_group_codes | No | World Bank income group codes, e.g. ["WB_HI","WB_LMI","WB_LI","WB_UMI"]. Use who_list_dimension_values with dimension="WORLDBANKINCOMEGROUP" to see all valid codes. Mutually exclusive with country_codes and region_codes. | |
| include_uncertainty | No | Include Low and High uncertainty interval bounds in output. Default true. |
Output Schema
| Name | Required | Description |
|---|---|---|
| rows | Yes | Data rows matching the query. |
| notice | No | Present when the limit was reached and not all rows were returned. Explains how to retrieve additional rows. |
| totalRows | Yes | Total row count matching the query on the server (before the limit is applied). |
| truncated | No | True when the result was capped at the requested limit. |
| totalCount | Yes | Alias of totalRows for cross-tool consistency — total rows before the limit. |
| appliedFilters | Yes | Filters that were applied to the query. |
who_search_indicatorsSearch WHO GHO IndicatorsRead-onlyIdempotentInspect
Search the WHO Global Health Observatory indicator catalog by keyword in the indicator name. Returns indicator codes and names for use with who_query_indicator_data. The search uses a substring match on indicator names — try terms like "life expectancy", "immunization", "mortality", "diabetes", or "HIV". If results are truncated, refine the query or use who_list_indicators to browse by offset.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of indicators to return. Default 20, max 100. | |
| query | Yes | Keyword to search in indicator names, e.g. "life expectancy" or "tuberculosis". |
Output Schema
| Name | Required | Description |
|---|---|---|
| notice | No | Present when the limit was reached and more results exist. Suggests how to get additional results. |
| indicators | Yes | Matching indicators up to the requested limit. |
| totalCount | Yes | Total indicators matching the query in the catalog, before the limit is applied. |
| effectiveQuery | Yes | Keyword used for the catalog search, as received by the server. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!