# Who Gho (npm · @pipeworx/mcp-who-gho) WHO GHO MCP — World Health Organization Global Health Observatory (free, no auth) - Trust score: 84/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-who-gho/who-gho-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-who-gho/who-gho-mcp) - npm · `@pipeworx/mcp-who-gho`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-who-gho/pipeworx-mcp-who-gho.md), [page](https://verifymcp.io/servers/pipeworx-io-who-gho/pipeworx-mcp-who-gho) ## Channel facts - Registry: `npm` - Package: `@pipeworx/mcp-who-gho` - Version: `0.2.0` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 100/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - No production dependencies, so there is no dependency health to assess. - **Provenance & Transparency**: 97/100 - Source repository is publicly reachable at the declared URL. - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-who-gho). - Clear OSI-approved license (MIT). - Actively maintained (last published 6 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 76/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 414 tokens (~138/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 23/100 - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the Who Gho MCP server? Who Gho runs locally as an npm package, launched with npx -y @pipeworx/mcp-who-gho. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add pipeworx-io-who-gho -- npx -y @pipeworx/mcp-who-gho ``` ### Cursor ```json { "mcpServers": { "pipeworx-io-who-gho": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-who-gho" ] } } } ``` ### VS Code ```json { "servers": { "pipeworx-io-who-gho": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-who-gho" ] } } } ``` ### Codex ```bash codex mcp add pipeworx-io-who-gho -- npx -y @pipeworx/mcp-who-gho ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "pipeworx-io-who-gho": { "type": "local", "command": [ "npx", "-y", "@pipeworx/mcp-who-gho" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add pipeworx-io-who-gho --command npx --arg -y --arg @pipeworx/mcp-who-gho ``` ### Hermes ```yaml mcp_servers: pipeworx-io-who-gho: command: "npx" args: ["-y", "@pipeworx/mcp-who-gho"] ``` ### Netclaw ```json { "McpServers": { "pipeworx-io-who-gho": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "@pipeworx/mcp-who-gho" ] } } } ``` ### Vellum ```bash assistant mcp add pipeworx-io-who-gho -t stdio -c npx -a -y @pipeworx/mcp-who-gho ``` ### Other ```json { "mcpServers": { "pipeworx-io-who-gho": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-who-gho" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 84, +1) No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-02 (score 83, +1) - [functional regression] Security disclosure: unverified → fail ### 2026-11-01 (score 82, 0) - [functional regression] Security disclosure: fail → unverified ### 2026-10-30 (score 82, +1) - [functional regression] Security disclosure: unverified → fail ### 2026-10-29 (score 81) First indexed and scored. ## MCP tools (3) ### `get_indicators` (~84 tokens) Search or list WHO Global Health Observatory indicators. Returns indicator codes and names. Use the indicator code with get_data to retrieve actual values. Example: get_indicators("life expectancy") or get_indicators("malaria") Input parameters: - `query` (string): Optional search keyword to filter indicators (e.g., "mortality", "tuberculosis"). Omit to list all. ### `get_data` (~215 tokens) Get World Health Organization health statistics for a country and year — life expectancy, immunization coverage, mortality, disease burden, risk factors and health system measures from the Global Health Observatory. Accepts a plain indicator name such as "measles immunization coverage" and a plain country name such as "Kenya"; both are resolved to WHO codes and the response says what it resolved to. If the requested year has no data it returns the latest year that does, and says which. Input parameters: - `country` (string): Country NAME ("Kenya", "United States") or ISO3 code ("KEN", "USA"). - `indicator` (string, required): Indicator NAME ("measles immunization coverage", "life expectancy at birth") or a GHO code ("mslv", "WHOSIS_000001"). Names are resolved — do not invent a code. - `year` (string): Year, e.g. "2020". If that year has no data the latest available year is returned instead, flagged as year_fallback. ### `list_countries` (~60 tokens) Return all WHO-recognized countries with their 3-letter ISO code, display name, and parent region code. Use the ISO codes returned here as the country parameter in get_data (e.g., "USA", "GBR", "JPN"). ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-who-gho/pipeworx-mcp-who-gho#diagnostics ## Score history - 2026-11-05: 84 - 2026-11-04: 84 - 2026-11-03: 83 - 2026-11-02: 83 - 2026-11-01: 82 - 2026-10-31: 82 - 2026-10-30: 82 - 2026-10-29: 81 ## Common questions ### What is the Who Gho MCP server? Who Gho is an MCP server listed in the public MCP registry as io.github.pipeworx-io/who-gho. WHO GHO MCP, World Health Organization Global Health Observatory (free, no auth). This page covers its npm package (@pipeworx/mcp-who-gho). ### Is the Who Gho MCP server safe to use? Who Gho scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Who Gho MCP server expose? Who Gho exposes 3 tools: get_indicators, get_data, list_countries. Their descriptions and schemas cost roughly 359 tokens of context every time the server is loaded. ### Is the Who Gho MCP server still maintained? Who Gho is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What licence is the Who Gho MCP server under? Who Gho declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ### What did VerifyMCP test on the Who Gho MCP server? VerifyMCP ran 16 checks on Who Gho, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - npm package: https://www.npmjs.com/package/@pipeworx/mcp-who-gho - Socket report: https://socket.dev/npm/package/@pipeworx/mcp-who-gho - Repository: https://github.com/pipeworx-io/mcp-who-gho - Website: https://pipeworx.io/packs/who-gho - Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-who-gho/pipeworx-mcp-who-gho.xml - Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-who-gho/pipeworx-mcp-who-gho/changelog.json - Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-who-gho/pipeworx-mcp-who-gho.json - HTML version of this page: https://verifymcp.io/servers/pipeworx-io-who-gho/pipeworx-mcp-who-gho