# Isrctn (npm · @pipeworx/mcp-isrctn)

ISRCTN — the UK-based international clinical trial registry (isrctn.com, part of Springer Nature /…

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 70/100, [markdown](https://verifymcp.io/servers/pipeworx-io-isrctn/isrctn-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-isrctn/isrctn-mcp)
- npm · `@pipeworx/mcp-isrctn`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-isrctn/pipeworx-mcp-isrctn.md), [page](https://verifymcp.io/servers/pipeworx-io-isrctn/pipeworx-mcp-isrctn)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-isrctn`
- 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-isrctn).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 574 tokens (~287/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**: 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 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.

## Install

### How do I install the Isrctn MCP server?

Isrctn runs locally as an npm package, launched with npx -y @pipeworx/mcp-isrctn. 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-isrctn -- npx -y @pipeworx/mcp-isrctn
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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, +27)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-02 (score 54, −25)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

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

First indexed and scored.

## MCP tools (2)

### `isrctn_search` (~391 tokens)

Search the ISRCTN registry (isrctn.com) — the UK-based international clinical trial registry — by free text and/or by condition/intervention. Use for "studies on <condition> and <drug/intervention>", "trials of psilocybin for depression", or any UK/international trial not necessarily registered on ClinicalTrials.gov. At least one of query/condition/intervention is required. Combining condition and intervention narrows to trials registered under BOTH (an AND, not an OR) — a real zero means no ISRCTN trial currently pairs that condition with that intervention, and the tool says so explicitly rather than guessing. `status` filters on a DERIVED recruitment status (ISRCTN's feed carries no status field) computed from each trial's recruitment dates — see `status_basis` on every returned trial.

Input parameters:

- `condition` (string): Filter to trials whose registered CONDITION field matches this phrase (e.g. "stroke", "treatment-resistant depression").
- `intervention` (string): Filter to trials whose registered INTERVENTION field matches this phrase (e.g. "psilocybin", "COMP360").
- `limit` (number): Max trials to return (1-50, default 10).
- `query` (string): Free-text search terms (title, summary, eligibility criteria, etc.) — e.g. "psilocybin" or "psilocybin depression" (multiple words are ANDed, not ORed). Optional if condition and/or intervention are…
- `status` (string): Filter on the DERIVED recruitment status (case-insensitive substring match) — e.g. "recruiting", "completed", "not yet recruiting". Applied client-side over the fetched batch (see `status_filter_scan…

### `isrctn_trial` (~127 tokens)

Look up a single ISRCTN trial by its registry number. Accepts "ISRCTN12345678", "isrctn12345678", or the bare number "12345678". Returns title, condition(s), intervention(s)/phase, derived recruitment status, sponsor, funder, dates, countries, and a note on whether results have been posted.

Input parameters:

- `id` (string, required): The ISRCTN trial number, with or without the "ISRCTN" prefix (e.g. "ISRCTN37167117" or "37167117").

## Diagnostics

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

## Score history

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

## Common questions

### What is the Isrctn MCP server?

Isrctn is an MCP server listed in the public MCP registry as io.github.pipeworx-io/isrctn. ISRCTN, the UK-based international clinical trial registry (isrctn.com, part of Springer Nature /… This page covers its npm package (@pipeworx/mcp-isrctn).

### Is the Isrctn MCP server safe to use?

Isrctn 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 Isrctn MCP server expose?

Isrctn exposes 2 tools: isrctn_search, isrctn_trial. Their descriptions and schemas cost roughly 518 tokens of context every time the server is loaded.

### Is the Isrctn MCP server still maintained?

Isrctn 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 Isrctn MCP server under?

Isrctn 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 Isrctn MCP server?

VerifyMCP ran 16 checks on Isrctn, 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-isrctn
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-isrctn
- Repository: https://github.com/pipeworx-io/mcp-isrctn
- Website: https://pipeworx.io/packs/isrctn
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-isrctn/pipeworx-mcp-isrctn.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-isrctn/pipeworx-mcp-isrctn/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-isrctn/pipeworx-mcp-isrctn.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-isrctn/pipeworx-mcp-isrctn