# Who Ictrp (npm · @pipeworx/mcp-who-ictrp) WHO ICTRP — the International Clinical Trials Registry Platform search portal… - Trust score: 78/100 (medium) - Change this week: 0 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `gateway.pipeworx.io`: 84/100, [markdown](https://verifymcp.io/servers/pipeworx-io-who-ictrp/who-ictrp-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-who-ictrp/who-ictrp-mcp) - npm · `@pipeworx/mcp-who-ictrp`: 78/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-who-ictrp/pipeworx-mcp-who-ictrp.md), [page](https://verifymcp.io/servers/pipeworx-io-who-ictrp/pipeworx-mcp-who-ictrp) ## Channel facts - Registry: `npm` - Package: `@pipeworx/mcp-who-ictrp` - 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-ictrp). - 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**: 57/100 - AI-judged instruction clarity (good). - 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. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 0/100 - Stability not yet verified: not enough scan history yet (needs a 30-day window). - **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 2 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 3 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. **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. ## Install ### 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. ### Claude ```bash claude mcp add pipeworx-io-who-ictrp -- npx -y @pipeworx/mcp-who-ictrp ``` ### Cursor ```json { "mcpServers": { "pipeworx-io-who-ictrp": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-who-ictrp" ] } } } ``` ### VS Code ```json { "servers": { "pipeworx-io-who-ictrp": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-who-ictrp" ] } } } ``` ### Codex ```bash codex mcp add pipeworx-io-who-ictrp -- npx -y @pipeworx/mcp-who-ictrp ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "pipeworx-io-who-ictrp": { "type": "local", "command": [ "npx", "-y", "@pipeworx/mcp-who-ictrp" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add pipeworx-io-who-ictrp --command npx --arg -y --arg @pipeworx/mcp-who-ictrp ``` ### Hermes ```yaml mcp_servers: pipeworx-io-who-ictrp: command: "npx" args: ["-y", "@pipeworx/mcp-who-ictrp"] ``` ### Netclaw ```json { "McpServers": { "pipeworx-io-who-ictrp": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "@pipeworx/mcp-who-ictrp" ] } } } ``` ### Vellum ```bash assistant mcp add pipeworx-io-who-ictrp -t stdio -c npx -a -y @pipeworx/mcp-who-ictrp ``` ### Other ```json { "mcpServers": { "pipeworx-io-who-ictrp": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-who-ictrp" ] } } } ``` ## 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-10-29 (score 78) First indexed and scored. ## MCP tools (2) ### `ictrp_search` (~404 tokens) 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. Input parameters: - `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". ### `ictrp_trial` (~193 tokens) 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. Input parameters: - `trial_id` (string, required): Registry trial id as the source registry writes it, e.g. "ChiCTR2400080001". ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-who-ictrp/pipeworx-mcp-who-ictrp#diagnostics ## Score history - 2026-11-05: 78 - 2026-11-04: 78 - 2026-11-03: 78 - 2026-11-02: 78 - 2026-11-01: 78 - 2026-10-31: 78 - 2026-10-30: 78 - 2026-10-29: 78 ## Common questions ### 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. ### What did VerifyMCP test on the Who Ictrp MCP server? VerifyMCP ran 15 checks on Who Ictrp, 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 Ictrp: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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-ictrp - Socket report: https://socket.dev/npm/package/@pipeworx/mcp-who-ictrp - Repository: https://github.com/pipeworx-io/mcp-who-ictrp - Website: https://pipeworx.io/packs/who-ictrp - Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-who-ictrp/pipeworx-mcp-who-ictrp.xml - Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-who-ictrp/pipeworx-mcp-who-ictrp/changelog.json - Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-who-ictrp/pipeworx-mcp-who-ictrp.json - HTML version of this page: https://verifymcp.io/servers/pipeworx-io-who-ictrp/pipeworx-mcp-who-ictrp