# Eu Ctis (npm · @pipeworx/mcp-eu-ctis)

EU CTIS MCP — the Clinical Trials Information System, the EU's public register of clinical trials…

- Trust score: 82/100 (high trust)
- Change this week: +4
- 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-eu-ctis/eu-ctis-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-eu-ctis/eu-ctis-mcp)
- npm · `@pipeworx/mcp-eu-ctis`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-eu-ctis/pipeworx-mcp-eu-ctis.md), [page](https://verifymcp.io/servers/pipeworx-io-eu-ctis/pipeworx-mcp-eu-ctis)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-eu-ctis`
- Version: `0.2.1`
- 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-eu-ctis).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - 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 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.

### Claude

```bash
claude mcp add pipeworx-io-eu-ctis -- npx -y @pipeworx/mcp-eu-ctis
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-eu-ctis -- npx -y @pipeworx/mcp-eu-ctis
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-eu-ctis --command npx --arg -y --arg @pipeworx/mcp-eu-ctis
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 82, +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.

### 2026-11-03 (score 81, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-01 (score 80, +1)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.07 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, +1)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (4)

### `ctis_search_trials` (~618 tokens)

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.

Input parameters:

- `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

### `ctis_trial` (~134 tokens)

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.

Input parameters:

- `ct_number` (string, required): CTIS trial number, e.g. "2025-523586-18-00"

### `ctis_trials_for_medicine` (~146 tokens)

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".

Input parameters:

- `country` (array): Restrict to these member states
- `limit` (number): Trials to return, 1-100 (default 25)
- `medicine` (string, required): Medicine, brand or active substance name, e.g. "semaglutide"
- `recruiting_only` (boolean): Only trials currently authorised or recruiting

### `ctis_recent_authorisations` (~163 tokens)

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.

Input parameters:

- `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

## Diagnostics

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

## Score history

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

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-eu-ctis
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-eu-ctis
- Repository: https://github.com/pipeworx-io/mcp-eu-ctis
- Website: https://pipeworx.io/packs/eu-ctis
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-eu-ctis/pipeworx-mcp-eu-ctis.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-eu-ctis/pipeworx-mcp-eu-ctis/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-eu-ctis/pipeworx-mcp-eu-ctis.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-eu-ctis/pipeworx-mcp-eu-ctis