Who Ictrp
NPM · @PIPEWORX/MCP-WHO-ICTRP · 2 COMPONENTS
WHO ICTRP — the International Clinical Trials Registry Platform search portal…
Available components
Last scanned (11 hours ago)
Scores higher than 58% 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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-who-ictrp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 656 tokens (~328/item across 2 items; 2 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 29 Oct 26 78
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-ictrp@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-ictrp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-who-ictrp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3561076501 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:901d670fb9966384d9c3bdb593f0bd09650f8cc8049ff87e8c62e0fdb1ae07c656b96f84243a9693aa9ce4a089809227a491089ad3b8413d93cf000e2 |
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 →
ictrp_search ~404
Search the WHO International Clinical Trials Registry Platform — one search across ClinicalTrials.gov and the WHO primary registries (ChiCTR China, jRCT/JPRN Japan, CTRI India, IRCT Iran, DRKS Germany, ANZCTR, ISRCTN, EU CTR/CTIS, CRIS Korea, ReBec Brazil, PACTR, TCTR and more). The way to find Chinese, Japanese, Indian and Iranian trials that ClinicalTrials.gov does not carry. Give a free-text query (searches titles, conditions and interventions, with WHO synonym expansion) and/or condition / intervention / sponsor fields; filter by source registry or recruiting status. Each row carries the trial id, its source registry, recruitment status, registration date and the ICTRP record URL — call ictrp_trial for the full record.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | – | Health condition, e.g. "stroke", "type 2 diabetes". |
| intervention | string | – | Intervention or drug, e.g. "metformin", "acupuncture". |
| limit | number | – | Rows to return, 1-100 (default 25). |
| query | string | – | Free text, e.g. "psilocybin" or "psilocybin depression". With condition/intervention/sponsor it is matched against the trial TITLE only. |
| recruiting_only | boolean | – | Only trials whose status is Recruiting. |
| registry | string | – | Keep only trials from one source registry: CT.gov, ANZCTR, ChiCTR, ITMCTR, CTRI, IRCT, DRKS, jRCT, JPRN, ISRCTN, EU-CTR, CTIS, CRIS, TCTR, PACTR, ReBec, LBCTR, NL-OMON, REPEC, SLCTR, RPCEC. Matched o… |
| sponsor | string | – | Primary sponsor name, e.g. "Fudan University". |
No output schema declared.
No examples provided.
ictrp_trial ~193
The WHO Trial Registration Data Set for one trial from any registry the WHO ICTRP covers, by its registry id (e.g. "ChiCTR2400080001", "CTRI/2024/01/061234", "IRCT20230101056789N1", "DRKS00031234", "jRCT2031230001", "NCT06123456", "ACTRN12626001215314"): source registry and its record URL, titles, primary sponsor, recruitment status, study type and design, phase, countries of recruitment, conditions, interventions, primary and secondary outcomes, eligibility (criteria, age range, sex), target sample size, dates, funding sources, secondary ids, ethics review status. Contact-person details are not returned.
| Name | Type | Req | Description |
|---|---|---|---|
| trial_id | string | yes | Registry trial id as the source registry writes it, e.g. "ChiCTR2400080001". |
No output schema declared.
No examples provided.
How do I install the Who Ictrp MCP server?
Who Ictrp runs locally as an npm package, launched with npx -y @pipeworx/mcp-who-ictrp. 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-ictrp
claude mcp add pipeworx-io-who-ictrp -- npx -y @pipeworx/mcp-who-ictrp
What is the Who Ictrp MCP server?
Who Ictrp is an MCP server listed in the public MCP registry as io.github.pipeworx-io/who-ictrp. WHO ICTRP, the International Clinical Trials Registry Platform search portal… This page covers its npm package (@pipeworx/mcp-who-ictrp).
Is the Who Ictrp MCP server safe to use?
Who Ictrp scores 78 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 Ictrp MCP server expose?
Who Ictrp exposes 2 tools: ictrp_search, ictrp_trial. Their descriptions and schemas cost roughly 597 tokens of context every time the server is loaded.
Is the Who Ictrp MCP server still maintained?
Who Ictrp 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 Ictrp MCP server under?
Who Ictrp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.