# Inxight Drugs (npm · @pipeworx/mcp-inxight-drugs)

Inxight Drugs — NCATS drug development status by indication.

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-inxight-drugs`
- 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-inxight-drugs).
  - 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**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 718 tokens (~239/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Inxight Drugs MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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-02 (score 80, +1)

- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `inxight_substance` (~237 tokens)

Drug development status by indication from NCATS Inxight Drugs: for one drug or substance (by name or FDA UNII), every condition it is approved for or in clinical trials for with the highest phase reached per condition (Approved, Phase III, Phase II, Phase I) and the trial or label behind it, plus the overall highest development event, first approval year and source, originator company, molecular targets with pharmacology and potency, synonyms, and cross-reference ids (ChEMBL, DrugBank, PubChem, CAS, MeSH, RxCUI). Answers "what is psilocybin being developed for and how far along", "which indications is this drug approved for", "is this compound still in trials".

Input parameters:

- `name` (string): Drug or substance name, brand or generic (e.g. "psilocybin", "aspirin", "semaglutide"). Give name or unii.
- `unii` (string): FDA Unique Ingredient Identifier, 10 characters (e.g. "2RV7212BP0" for psilocybin). Takes precedence over name.

### `inxight_search` (~209 tokens)

Search NCATS Inxight Drugs substances by free text (drug name, synonym, code, company or condition words), optionally narrowed to a development status (US Approved Rx, US Approved OTC, US Previously Marketed, Possibly Marketed Outside US, Clinical, Other). Returns matching substances with FDA UNII and class, the total hit count, and breakdowns of the matches by development status, highest phase and top conditions. Use it to find the UNII to pass to inxight_substance or to scan, e.g., which psychedelics are in clinical development.

Input parameters:

- `development_status` (string): Only substances whose overall development status is this value
- `limit` (number): Results to return, 1-50 (default 10)
- `offset` (number): Results to skip, for paging (default 0)
- `query` (string, required): Free-text query, e.g. "psilocybin", "GLP-1", "tryptamine"

### `inxight_indication` (~214 tokens)

Drugs and substances approved for or in clinical development for a condition, from NCATS Inxight Drugs: give a disease or indication (e.g. "stroke", "major depressive disorder", "migraine") and get each substance with the highest phase it has reached FOR THAT CONDITION, the trial or label URL behind it, and its FDA UNII. Narrow with development_status "Clinical" to see only investigational drugs. Also returns the related condition labels Inxight uses (e.g. "Ischemic stroke", "Acute ischemic stroke") so a caller can drill down.

Input parameters:

- `condition` (string, required): Disease or indication, e.g. "stroke", "Alzheimer disease"
- `development_status` (string): Only substances whose overall development status is this value; "Clinical" = investigational only
- `limit` (number): Substances to return, 1-25 (default 10)
- `offset` (number): Substances to skip, for paging (default 0)

## Diagnostics

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

## Score history

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

## Common questions

### What is the Inxight Drugs MCP server?

Inxight Drugs is an MCP server listed in the public MCP registry as io.github.pipeworx-io/inxight-drugs. Inxight Drugs, NCATS drug development status by indication. This page covers its npm package (@pipeworx/mcp-inxight-drugs).

### Is the Inxight Drugs MCP server safe to use?

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

Inxight Drugs exposes 3 tools: inxight_substance, inxight_search, inxight_indication. Their descriptions and schemas cost roughly 660 tokens of context every time the server is loaded.

### Is the Inxight Drugs MCP server still maintained?

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

Inxight Drugs 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 Inxight Drugs MCP server?

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