Eu Ctis
NPM · @PIPEWORX/MCP-EU-CTIS · 2 COMPONENTS
EU CTIS MCP — the Clinical Trials Information System, the EU's public register of clinical trials…
Available components
Last scanned (16 hours ago)
Scores higher than 72% 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-eu-ctis). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1118 tokens (~279/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 (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 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-eu-ctis@0.2.1
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-eu-ctis |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-eu-ctis/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635930845 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e1db2caeabe34f54427d1c2189314e280cd3cf9575a93149c5a8899307bc97fe3b571da737f56bf50cd50647a958d1dc1591225579c8c340839e15afe |
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 →
ctis_recent_authorisations ~163
Clinical trials most recently authorised in the EU/EEA, newest decision first, from the EU Clinical Trials Information System. Optionally narrowed to a member state, a medical condition, a sponsor or a phase. Answers "what did the EU authorise this month" and shows what sponsors are starting in Europe now.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | – | Medical condition, e.g. "breast cancer" |
| country | array | – | Member states concerned |
| limit | number | – | Trials to return, 1-100 (default 25) |
| phase | array | – | Trial phase, e.g. ["3"] |
| since | string | – | Only decisions on or after this date, YYYY-MM-DD |
| sponsor | string | – | Sponsor organisation name |
No output schema declared.
No examples provided.
ctis_search_trials ~618
Search clinical trials authorised in the EU/EEA under Regulation 536/2014, from the EU Clinical Trials Information System (CTIS). Filter by medicine or active substance, medical condition, sponsor, trial status, phase, member state, age group, sex, results availability and start date. Returns trial number, title, status, sponsor, phase, conditions, products, per-country status, enrolment and primary endpoint. Answers questions such as which European trials are recruiting for a drug, who sponsors them and which member states they run in.
| Name | Type | Req | Description |
|---|---|---|---|
| age_group | array | – | Age range of subjects: "in utero", "0-17 years", "18-64 years", "65+ years" |
| condition | string | – | Medical condition studied, e.g. "melanoma" |
| country | array | – | EEA member states concerned, by name or ISO code, e.g. ["Germany", "ES"] |
| endpoint | string | – | Words appearing in the trial endpoints |
| exclude | string | – | Terms that must NOT appear in the record |
| gender | string | – | Restrict to trials enrolling "male" or "female" subjects |
| has_results | boolean | – | Only trials that have posted study results |
| limit | number | – | Results per page, 1-100 (default 20) |
| low_intervention | boolean | – | Only low-intervention trials |
| medicine | string | – | Medicine, brand or active substance name, e.g. "pembrolizumab" |
| orphan_designation | boolean | – | Only trials of a product with an orphan designation |
| page | number | – | Result page, 1-based |
| phase | array | – | Trial phase — "1", "2", "3", "4" (or "phase III"), which expands to the integrated phases too |
| query | string | – | Free-text terms matched across the trial record (any of the words) |
| rare_disease | boolean | – | Only trials in a rare disease |
| region | string | – | Where the trial runs: "EEA only", "non-EEA only" or "both" |
| sort_by | string | – | Sort field: decisionDate (default), ctNumber, sponsor, ctStatus |
| sort_direction | string | – | ASC or DESC (default DESC) |
| sponsor | string | – | Sponsor organisation name, e.g. "Novartis" |
| start_from | string | – | Earliest EEA start date, YYYY-MM-DD |
| start_to | string | – | Latest EEA start date, YYYY-MM-DD |
| status | array | – | Trial status: "Under evaluation", "Authorised, recruitment pending", "Authorised, recruiting", "Ongoing, recruiting", "Ongoing, recruitment ended", "Temporarily halted", "Suspended", "Ended", "Expire… |
| title | string | – | Words that must appear in the trial title |
No output schema declared.
No examples provided.
ctis_trial ~134
Full published record for one EU clinical trial by its CTIS number (e.g. 2025-523586-18-00): full scientific title, sponsor and contacts, investigational products with active substances and roles, medical conditions, therapeutic areas, trial objective, eligibility criteria, primary and secondary endpoints, planned enrolment, estimated end date, and the authorisation status, decision date and reported start and recruitment events in each member state. Sourced from the EU Clinical Trials Information System.
| Name | Type | Req | Description |
|---|---|---|---|
| ct_number | string | yes | CTIS trial number, e.g. "2025-523586-18-00" |
No output schema declared.
No examples provided.
ctis_trials_for_medicine ~146
Every EU/EEA clinical trial involving a named medicine or active substance, from the EU Clinical Trials Information System, newest authorisation first. Splits the result by trial status so it is clear how many are still recruiting versus ended, and lists sponsors and member states. Answers "what is running in Europe for this drug".
| Name | Type | Req | Description |
|---|---|---|---|
| country | array | – | Restrict to these member states |
| limit | number | – | Trials to return, 1-100 (default 25) |
| medicine | string | yes | Medicine, brand or active substance name, e.g. "semaglutide" |
| recruiting_only | boolean | – | Only trials currently authorised or recruiting |
No output schema declared.
No examples provided.
How do I install the Eu Ctis MCP server?
Eu Ctis runs locally as an npm package, launched with npx -y @pipeworx/mcp-eu-ctis. 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-eu-ctis
claude mcp add pipeworx-io-eu-ctis -- npx -y @pipeworx/mcp-eu-ctis
What is the Eu Ctis MCP server?
Eu Ctis is an MCP server listed in the public MCP registry as io.github.pipeworx-io/eu-ctis. EU CTIS MCP, the Clinical Trials Information System, the EU's public register of clinical trials… This page covers its npm package (@pipeworx/mcp-eu-ctis).
Is the Eu Ctis MCP server safe to use?
Eu Ctis scores 82 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 Eu Ctis MCP server expose?
Eu Ctis exposes 4 tools: ctis_search_trials, ctis_trial, ctis_trials_for_medicine, ctis_recent_authorisations. Their descriptions and schemas cost roughly 1,061 tokens of context every time the server is loaded.
Is the Eu Ctis MCP server still maintained?
Eu Ctis 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 Eu Ctis MCP server under?
Eu Ctis 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 Eu Ctis MCP server?
VerifyMCP ran 16 checks on Eu Ctis, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.