# Rxnorm (npm · @pipeworx/mcp-rxnorm)

RxNorm MCP — wraps the NLM RxNav REST API (free, no auth)

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-rxnorm`
- 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-rxnorm).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 695 tokens (~173/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 Rxnorm MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-04 (score 83, +1)

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

### 2026-11-02 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-31 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

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

First indexed and scored.

## MCP tools (4)

### `rxnorm_search` (~162 tokens)

Look up a medication's RxCUI and MAP A BRAND DRUG TO ITS GENERIC INGREDIENT (and vice versa) — e.g. Eliquis -> apixaban, Lipitor -> atorvastatin. Search by brand or generic name; returns RxCUI IDs, names, synonyms, and term types (BN=brand, IN=ingredient, SBD=dose form). The right tool for "what is the RxCUI for X", "what generic ingredient does brand X map to", or "brand vs generic name". Start here to find a drug's unique ID.

Input parameters:

- `name` (string, required): Drug name to search for — brand or generic (e.g., "Ozempic", "semaglutide", "metformin")

### `rxnorm_get_properties` (~96 tokens)

Get full medication details by RxCUI ID. Returns name, synonyms, term type, language, and status. Use after rxnorm_search to retrieve complete drug information.

Input parameters:

- `rxcui` (string, required): RxNorm concept ID (e.g., "7052" for metformin) OR a drug name (e.g. "aspirin", "Tylenol") — names are resolved to an RxCUI automatically.

### `rxnorm_related` (~206 tokens)

Find related medications by RxCUI — brands, generics, ingredients, and dose forms. Maps between brand and generic alternatives. Use to compare drug options.

Input parameters:

- `rxcui` (string, required): RxNorm concept ID, or a drug name (e.g. "aspirin") — resolved to an RxCUI automatically.
- `tty` (string): Optional term type filter: BN (brand name), IN (ingredient), SBD (semantic branded drug), SCD (semantic clinical drug), GPCK (generic pack), BPCK (branded pack); other RxNorm term types such as PIN,…

### `rxnorm_ndc` (~178 tokens)

Get the NDC (National Drug Code) identifiers for a drug — the 11-digit US pharmacy codes used for billing, dispensing and inventory. Takes an RxCUI or a plain drug name ("amoxicillin", "Lipitor"). NDCs attach to marketed products rather than to an ingredient, so an ingredient or brand name is expanded to its products automatically and the response says it did so; a concept with nothing currently marketed reports its historical NDC count instead of an unexplained empty list.

Input parameters:

- `rxcui` (string, required): RxNorm concept ID, or a drug name — resolved to an RxCUI automatically. A bare ingredient ("amoxicillin") works: it is expanded to its marketed products. A full dose phrase ("lisinopril 10 mg oral ta…

## Diagnostics

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

## Score history

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

## Common questions

### What is the Rxnorm MCP server?

Rxnorm is an MCP server listed in the public MCP registry as io.github.pipeworx-io/rxnorm. RxNorm MCP, wraps the NLM RxNav REST API (free, no auth). This page covers its npm package (@pipeworx/mcp-rxnorm).

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

Rxnorm scores 83 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 Rxnorm MCP server expose?

Rxnorm exposes 4 tools: rxnorm_search, rxnorm_get_properties, rxnorm_related, rxnorm_ndc. Their descriptions and schemas cost roughly 642 tokens of context every time the server is loaded.

### Is the Rxnorm MCP server still maintained?

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

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

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