io.github.cyanheads/who-gho-mcp-server
REMOTE · WHO-GHO.CASEYJHAND.COM · 2 COMPONENTS · SCANNED AUG 3
WHO Global Health Observatory — 3,059 indicators across 194 member states.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1273 tokens (~212/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · who-gho.caseyjhand.com
claude mcp add --transport http cyanheads-who-gho-mcp-server https://who-gho.caseyjhand.com/mcp
[mcp_servers.cyanheads-who-gho-mcp-server] url = "https://who-gho.caseyjhand.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cyanheads-who-gho-mcp-server": {
"type": "remote",
"url": "https://who-gho.caseyjhand.com/mcp",
"enabled": true
}
}
} openclaw mcp add cyanheads-who-gho-mcp-server --url https://who-gho.caseyjhand.com/mcp --transport streamable-http
mcp_servers:
cyanheads-who-gho-mcp-server:
url: "https://who-gho.caseyjhand.com/mcp" {
"mcpServers": {
"cyanheads-who-gho-mcp-server": {
"type": "http",
"url": "https://who-gho.caseyjhand.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://who-gho.caseyjhand.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=caseyjhand.com | CN=WE1,O=Google Trust Services,C=US | 7 Jul 2026 | 5 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 5aad900eb2055a0b0ea55912ec19680c |
| SANs: caseyjhand.com, *.caseyjhand.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC secure
Validation of who-gho.caseyjhand.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| caseyjhand.com. | present | 2371 | 13 | Verified |
| who-gho.caseyjhand.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://who-gho.caseyjhand.com/mcp | Verified | 200 | |
| http (plaintext) | http://who-gho.caseyjhand.com/mcp | HTTPS enforced | 301 | https://who-gho.caseyjhand.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
who_get_indicator_metadata Get WHO GHO Indicator Metadata ~138
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 | Type | Req | Description |
|---|---|---|---|
| indicator_codes | array | yes | One to ten indicator codes, e.g. ["WHOSIS_000001", "MDG_0000000026"]. |
| Name | Type | Req | Description |
|---|---|---|---|
| indicators | array | yes | Metadata for each code that returned results. |
| notFound | array | yes | Indicator codes that returned no metadata — they may not exist in the GHO catalog. |
No examples provided.
who_list_dimension_values List GHO Dimension Values ~121
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 | Type | Req | Description |
|---|---|---|---|
| dimension | string | yes | Dimension type code. Use who_list_dimensions to discover all available codes. Common values: COUNTRY, REGION, SEX, WORLDBANKINCOMEGROUP, AGEGROUP. |
| Name | Type | Req | Description |
|---|---|---|---|
| dimension | string | yes | The requested dimension type code. |
| values | array | yes | Valid values for this dimension type. |
No examples provided.
who_list_dimensions List GHO Dimension Types ~75
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | array | yes | All available dimension types in the GHO catalog. |
No examples provided.
who_list_indicators List WHO GHO Indicators ~93
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 | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Number of indicators to return per page. Default 50, max 500. |
| offset | integer | — | Zero-based offset for pagination. Default 0. |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | True when more indicators exist beyond the current page. |
| indicators | array | yes | Indicators for the requested page. |
| pageInfo | string | yes | Human-readable page position, e.g. "offset 0, showing 50 of 3059". Use to construct the next offset. |
| totalCount | number | yes | Total number of indicators in the GHO catalog. |
No examples provided.
who_query_indicator_data Query WHO GHO Indicator Data ~633
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 | Type | Req | Description |
|---|---|---|---|
| country_codes | array | — | ISO 3166-1 alpha-3 country codes to filter on, e.g. ["JPN","USA","BRA"]. Mutually exclusive with region_codes and income_group_codes. |
| dim1_value | string | — | 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. |
| include_uncertainty | boolean | — | Include Low and High uncertainty interval bounds in output. Default true. |
| income_group_codes | array | — | 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_co… |
| indicator_code | string | yes | Indicator code to query, e.g. "WHOSIS_000001". Use who_search_indicators to find codes. |
| limit | integer | — | Maximum number of data rows to return. Default 200, max 1000. |
| region_codes | array | — | 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 regio… |
| sex | string | — | 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. |
| year_from | integer | — | Start year (inclusive) for the time range filter, e.g. 2015. |
| year_to | integer | — | End year (inclusive) for the time range filter, e.g. 2023. |
| Name | Type | Req | Description |
|---|---|---|---|
| appliedFilters | object | yes | Filters that were applied to the query. |
| notice | string | — | Present when the limit was reached and not all rows were returned. Explains how to retrieve additional rows. |
| rows | array | yes | Data rows matching the query. |
| totalCount | number | yes | Alias of totalRows for cross-tool consistency — total rows before the limit. |
| totalRows | number | yes | Total row count matching the query on the server (before the limit is applied). |
| truncated | boolean | — | True when the result was capped at the requested limit. |
No examples provided.
who_search_indicators Search WHO GHO Indicators ~139
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 | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Maximum number of indicators to return. Default 20, max 100. |
| query | string | yes | Keyword to search in indicator names, e.g. "life expectancy" or "tuberculosis". |
| Name | Type | Req | Description |
|---|---|---|---|
| effectiveQuery | string | yes | Keyword used for the catalog search, as received by the server. |
| indicators | array | yes | Matching indicators up to the requested limit. |
| notice | string | — | Present when the limit was reached and more results exist. Suggests how to get additional results. |
| totalCount | number | yes | Total indicators matching the query in the catalog, before the limit is applied. |
No examples provided.