io.github.cyanheads/who-gho-mcp-server
REMOTE · WHO-GHO.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 28
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 → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1670 tokens (~278/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.cyanheads/who-gho-mcp-server server?
io.github.cyanheads/who-gho-mcp-server is a hosted endpoint at https://who-gho.caseyjhand.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · who-gho.caseyjhand.com
claude mcp add --transport http cyanheads-who-gho-mcp-server 'https://who-gho.caseyjhand.com/mcp'
{
"mcpServers": {
"cyanheads-who-gho-mcp-server": {
"url": "https://who-gho.caseyjhand.com/mcp"
}
}
} {
"servers": {
"cyanheads-who-gho-mcp-server": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://who-gho.caseyjhand.com/mcp"
}
}
} assistant mcp add cyanheads-who-gho-mcp-server -t streamable-http -u '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.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 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
- 20 Sept 26 0
- Server version: 0.3.4 → 0.3.5 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 −1
- Stability: pass → 0.93 functional
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.3.3 → 0.3.4 functional
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 28 Sept 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 | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a6985204ed51ae050e7738aa6be668e9 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
who_get_indicator_metadata Get WHO GHO Indicator Metadata ~171
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. Many valid indicators have no dimension listing upstream — those return an empty dimensions array with a dimensionsNote, not a not-found. Only codes absent from the catalog are reported in the notFound array, and that is reported rather than raised as 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 |
|---|---|---|---|
| error | object | – | Present when the call failed. Absent on success. |
| indicators | array | – | Metadata for each code that resolved to a catalog entry. |
| notFound | array | – | Indicator codes that resolved to neither a catalog name nor any dimension rows — they do not exist in the GHO catalog. |
No examples provided.
who_list_dimension_values List GHO Dimension Values ~288
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. Results are paged in a deterministic order — narrow hierarchical dimensions with parent_code (e.g. the countries in one WHO region), and page the rest with offset.
| 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. |
| limit | integer | – | Number of values to return per page. Default 100, max 500. |
| offset | integer | – | Zero-based offset into the values for this dimension and filter. Default 0. Read hasMore and nextOffset from the response to continue paging. An offset at or beyond totalCount returns an empty values… |
| parent_code | string | – | Restrict results to values under one parent, e.g. dimension="COUNTRY" with parent_code="EUR" for the countries in the WHO European Region. Only hierarchical dimensions carry a parent; a filter that m… |
| Name | Type | Req | Description |
|---|---|---|---|
| dimension | string | – | The requested dimension type code. |
| error | object | – | Present when the call failed. Absent on success. |
| hasMore | boolean | – | True when more values remain beyond this page. Pair with nextOffset to continue. |
| nextOffset | number | – | Offset to request for the next page. Absent when this page reached the end of the values. |
| notice | string | – | Present when values were withheld, the parent_code filter matched nothing, or the requested offset ran past the end. Explains what to do next. |
| offset | number | – | Zero-based offset this page started at. |
| pageInfo | string | – | Human-readable page position, e.g. "offset 0, showing 100 of 234". Use to construct the next offset. |
| totalCount | number | – | Total values for this dimension and filter, before the limit is applied. |
| values | array | – | Valid values for this dimension type, for the requested page. |
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 | – | All available dimension types in the GHO catalog. |
| error | object | – | Present when the call failed. Absent on success. |
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 |
|---|---|---|---|
| error | object | – | Present when the call failed. Absent on success. |
| hasMore | boolean | – | True when more indicators exist beyond the current page. |
| indicators | array | – | Indicators for the requested page. |
| pageInfo | string | – | Human-readable page position, e.g. "offset 0, showing 50 of 3059". Use to construct the next offset. |
| totalCount | number | – | Total number of indicators in the GHO catalog. |
No examples provided.
who_query_indicator_data Query WHO GHO Indicator Data ~779
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. Rows are returned in a deterministic order (most recent first by default), so a capped result is the top of a defined slice rather than an arbitrary sample; page through the rest with offset.
| 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. |
| offset | integer | – | Zero-based row offset for pagination. Default 0. Pages are stable because rows are returned in a deterministic order — read hasMore and nextOffset from the response to continue. An offset at or beyon… |
| 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. |
| sort | string | – | Row ordering: "year_desc" (default) returns the most recent years first, "year_asc" the earliest first. Ties are broken by spatial code, then dimension, then row id. |
| 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 | – | Filters that were applied to the query. |
| error | object | – | Present when the call failed. Absent on success. |
| hasMore | boolean | – | True when rows remain beyond this page. Pair with nextOffset to continue. |
| nextOffset | number | – | Offset to request for the next page. Absent when this page reached the end of the result set. |
| notice | string | – | Present when rows were withheld or the requested offset ran past the end of the result set. Explains how to reach the remaining rows. |
| offset | number | – | Zero-based row offset this page started at. |
| pageInfo | string | – | Human-readable page position, e.g. "offset 0, showing 200 of 12936". Use to construct the next offset. |
| rows | array | – | Data rows matching the query. |
| totalCount | number | – | Alias of totalRows for cross-tool consistency — total rows before the limit. |
| totalRows | number | – | 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 ~190
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 page further into the same filtered result set with offset.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of indicators to return. Default 20, max 100. |
| offset | integer | – | Zero-based offset into the matches for this query. Default 0. Read hasMore and nextOffset from the response to continue paging. An offset at or beyond totalCount returns an empty indicators array, no… |
| query | string | yes | Keyword to search in indicator names, e.g. "life expectancy" or "tuberculosis". |
| Name | Type | Req | Description |
|---|---|---|---|
| effectiveQuery | string | – | Keyword used for the catalog search, as received by the server. |
| error | object | – | Present when the call failed. Absent on success. |
| hasMore | boolean | – | True when more matches remain beyond this page. Pair with nextOffset to continue. |
| indicators | array | – | Matching indicators up to the requested limit. |
| nextOffset | number | – | Offset to request for the next page. Absent when this page reached the end of the matches. |
| notice | string | – | Present when matches were withheld or the requested offset ran past the end of the result set. Explains how to reach the remaining matches. |
| offset | number | – | Zero-based offset this page started at. |
| pageInfo | string | – | Human-readable page position, e.g. "offset 0, showing 20 of 3003". Use to construct the next offset. |
| totalCount | number | – | Total indicators matching the query in the catalog, before the limit is applied. |
No examples provided.
What is the io.github.cyanheads/who-gho-mcp-server server?
io.github.cyanheads/who-gho-mcp-server is listed in the public MCP registry as io.github.cyanheads/who-gho-mcp-server. WHO Global Health Observatory, 3,059 indicators across 194 member states. This page covers its hosted endpoint (https://who-gho.caseyjhand.com/mcp).
Is the io.github.cyanheads/who-gho-mcp-server server safe to use?
io.github.cyanheads/who-gho-mcp-server scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.cyanheads/who-gho-mcp-server server expose?
io.github.cyanheads/who-gho-mcp-server exposes 6 tools: who_list_dimensions, who_list_dimension_values, who_search_indicators, who_list_indicators, who_get_indicator_metadata, who_query_indicator_data. Their descriptions and schemas cost roughly 1,596 tokens of context every time the server is loaded.
Does the io.github.cyanheads/who-gho-mcp-server server require authentication?
No. We connected to io.github.cyanheads/who-gho-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cyanheads/who-gho-mcp-server server still maintained?
io.github.cyanheads/who-gho-mcp-server is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.