Who Euro MCP Server

@pipeworx/who-euro

Health statistics for the WHO European Region — 2,657 indicators across 22 datasets and 53 countries, many with series running back to the 1970s. Sourced from the WHO Regional Office for Europe Data Warehouse API v5.

Part of Pipeworx — an MCP gateway connecting AI agents to 1867+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

Two things to know before editing

The host is not in WHO's own docs. The published API specification writes the base as http://HOST/api/v5/… — a literal placeholder. The real host (dw.euro.who.int) appears only in the gateway site's page markup. Anything under gateway.euro.who.int/api/… returns 404.

There is no text search. ?search=, ?q=, ?name= all return 400 invalid parameter. The only filter is:

?filter=ATTRIBUTE:CODES_LIST;ATTRIBUTE:CODES_LIST
        e.g. COUNTRY:UKR;YEAR:2015-2020;SEX:ALL

…over structured dimension codes, never over names. So searching by wording happens in this pack, over the full measures list, which is fetched once per isolate and memoised. CODES_LIST also supports *, $blank, ranges (1999-2004), and nearest-year lookups (~2001).

Indicator names work, not just codes

who_euro_measure_data accepts an indicator name as well as a code. This is not a convenience — codes like HFA_1 are unguessable, and a model asked for data will invent one. A live routing test for "tuberculosis incidence in Ukraine" produced HFA_468, which is rural sewage access. Responses carry measure_resolution saying what the name resolved to, plus other candidates when the wording is ambiguous.

Coverage note

WHO/Europe advertises "8,000+ indicators". The v5 API returns 2,657 measures in English — the larger figure appears to count across languages, datasets, or retired series. The pack reports what the API actually serves.

Auth

None.

Known upstream quirk

dw.euro.who.int presents an incomplete certificate chain — leaf only, no intermediate (Sectigo DV R36). curl completes it from its own store; strict TLS clients such as Node's undici reject it with UNABLE_TO_VERIFY_LEAF_SIGNATURE. If a connection fails, the pack says so explicitly rather than returning a bare "fetch failed", which would read like a WHO outage.

Data sources

• WHO/Europe Data Warehouse API — https://dw.euro.who.int/api/v5/version
• API specification — https://gateway.euro.who.int/en/api/specification/
• European Health Information Gateway — https://gateway.euro.who.int/

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "who-euro": {
      "url": "https://gateway.pipeworx.io/who-euro/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/who-euro/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1867+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/who_euro_search_measures \
  -H 'Content-Type: application/json' \
  -d '{"query":"tuberculosis"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/who_euro_search_measures. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-who-euro is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/who-euro/mcp endpoint shown above. It needs network access; there is no offline mode.

{
  "mcpServers": {
    "who-euro": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-who-euro"]
    }
  }
}

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Who Euro data" })

The gateway picks the right tool and fills the arguments automatically.

More

• Docs and guides
• pipeworx.io

License

MIT