# Who Tb (npm · @pipeworx/mcp-who-tb)

WHO Global Tuberculosis Programme — the TME data collection.

- Trust score: 79/100 (medium)
- Change this week: −2
- 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-tb/who-tb-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-who-tb/who-tb-mcp)
- npm · `@pipeworx/mcp-who-tb`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-who-tb/pipeworx-mcp-who-tb.md), [page](https://verifymcp.io/servers/pipeworx-io-who-tb/pipeworx-mcp-who-tb)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-who-tb`
- 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**: 71/100
  - Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-who-tb).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 547 tokens (~136/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Tb MCP server?

Who Tb runs locally as an npm package, launched with npx -y @pipeworx/mcp-who-tb. 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-tb -- npx -y @pipeworx/mcp-who-tb
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-who-tb": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-who-tb"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-who-tb": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-who-tb"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-who-tb -- npx -y @pipeworx/mcp-who-tb
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-who-tb": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-who-tb"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-who-tb --command npx --arg -y --arg @pipeworx/mcp-who-tb
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-who-tb:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-who-tb"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-who-tb": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-who-tb"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-who-tb -t stdio -c npx -a -y @pipeworx/mcp-who-tb
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-who-tb": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-who-tb"
      ]
    }
  }
}
```

## 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-05 (score 79, −5)

- [security regression] Provenance: pass → unverified

### 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)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 82, +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.

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (4)

### `who_tb_estimates` (~158 tokens)

WHO estimates of tuberculosis burden by country and year — TB incidence per 100 000 and in absolute cases with uncertainty ranges, TB mortality, the share of TB cases that are HIV-positive, and case detection rate. Covers 217 countries from 2000 onward. Use for questions about how much tuberculosis a country has, TB death rates, and TB trends over time.

Input parameters:

- `country` (string): Country name or ISO code, e.g. "India", "IND", "KE". Omit for all countries.
- `limit` (number): Maximum rows (default 100).
- `years` (string): Year or range, e.g. "2023" or "2015-2023". Omit for all years.

### `who_tb_notifications` (~120 tokens)

Tuberculosis cases actually notified to WHO by national TB programmes, by country and year — new and relapse cases, laboratory-confirmed versus clinically diagnosed, and HIV testing coverage among notified cases. Notifications are reported cases, which is a different measure from estimated incidence. Use for questions about diagnosed and reported TB cases.

Input parameters:

- `country` (string): Country name or ISO code.
- `limit` (number): Maximum rows (default 100).
- `years` (string): Year or range, e.g. "2023" or "2015-2023".

### `who_tb_budget` (~97 tokens)

National tuberculosis programme financing by country and year — total TB budget, and budgeted cost per patient for drug-susceptible and multidrug-resistant TB treatment, with patients expected to be treated. Use for questions about TB programme funding and the cost of TB treatment.

Input parameters:

- `country` (string): Country name or ISO code.
- `limit` (number): Maximum rows (default 100).
- `years` (string): Year or range.

### `who_tb_dictionary` (~117 tokens)

Explain the column names used in WHO tuberculosis data — what e_inc_100k, c_newinc, e_mort_num or budget_cpp_mdr actually mean, which dataset each belongs to, and its definition. Use to interpret a WHO TB field before reporting a number, or to find which variable answers a question.

Input parameters:

- `limit` (number): Maximum entries (default 50).
- `query` (string): A variable name ("e_inc_100k") or words from its definition ("incidence"). Omit to list all.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-who-tb/pipeworx-mcp-who-tb#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### What is the Who Tb MCP server?

Who Tb is an MCP server listed in the public MCP registry as io.github.pipeworx-io/who-tb. WHO Global Tuberculosis Programme, the TME data collection. This page covers its npm package (@pipeworx/mcp-who-tb).

### Is the Who Tb MCP server safe to use?

Who Tb scores 79 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 Tb MCP server expose?

Who Tb exposes 4 tools: who_tb_estimates, who_tb_notifications, who_tb_budget, who_tb_dictionary. Their descriptions and schemas cost roughly 492 tokens of context every time the server is loaded.

### Is the Who Tb MCP server still maintained?

Who Tb 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 Tb MCP server under?

Who Tb 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 Tb MCP server?

VerifyMCP ran 15 checks on Who Tb, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Who Tb: Provenance. 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-tb
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-who-tb
- Repository: https://github.com/pipeworx-io/mcp-who-tb
- Website: https://pipeworx.io/packs/who-tb
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-who-tb/pipeworx-mcp-who-tb.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-who-tb/pipeworx-mcp-who-tb/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-who-tb/pipeworx-mcp-who-tb.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-who-tb/pipeworx-mcp-who-tb