Who Tb
NPM · @PIPEWORX/MCP-WHO-TB · 2 COMPONENTS
WHO Global Tuberculosis Programme — the TME data collection.
Available components
Last scanned (7 hours ago)
Scores higher than 62% of npm servers
Category Health and Science
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
- 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. View diagnostics → Unverified
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-who-tb). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Provenance in Provenance & TransparencyRepository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 −5
- Provenance: pass → unverified ▼ security
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 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.
- 29 Oct 26 81
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-who-tb@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-who-tb |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-who-tb/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3561083489 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:23f76159a274b8ac01f76288d18ad5b2b1d2559e94e9301ea0da76bd76ccc663b70a2c45dd268ba33cb6f347ac0924f33492dfeb07d987a613b73d87d |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_tb_budget ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country name or ISO code. |
| limit | number | – | Maximum rows (default 100). |
| years | string | – | Year or range. |
No output schema declared.
No examples provided.
who_tb_dictionary ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum entries (default 50). |
| query | string | – | A variable name ("e_inc_100k") or words from its definition ("incidence"). Omit to list all. |
No output schema declared.
No examples provided.
who_tb_estimates ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
who_tb_notifications ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country name or ISO code. |
| limit | number | – | Maximum rows (default 100). |
| years | string | – | Year or range, e.g. "2023" or "2015-2023". |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-who-tb
claude mcp add pipeworx-io-who-tb -- npx -y @pipeworx/mcp-who-tb
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.