Rxnorm
NPM · @PIPEWORX/MCP-RXNORM · 2 COMPONENTS
RxNorm MCP — wraps the NLM RxNav REST API (free, no auth)
Available components
Last scanned (8 hours ago)
Scores higher than 76% 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-rxnorm). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. 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
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.
- 4 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 2 Nov 26 +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.
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 +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.
- 29 Oct 26 80
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-rxnorm@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-rxnorm |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-rxnorm/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691892750 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:634b376709494e5dadb0a6ec011aaeb7e223e3fe171a41da7ae9488bf9baf4e1918f8301565eec19c64ebd9752b68783a5cff09c3aefc1e3c0bb73ffb |
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 →
rxnorm_get_properties ~96
Get full medication details by RxCUI ID. Returns name, synonyms, term type, language, and status. Use after rxnorm_search to retrieve complete drug information.
| Name | Type | Req | Description |
|---|---|---|---|
| rxcui | string | yes | RxNorm concept ID (e.g., "7052" for metformin) OR a drug name (e.g. "aspirin", "Tylenol") — names are resolved to an RxCUI automatically. |
No output schema declared.
No examples provided.
rxnorm_ndc ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| rxcui | string | yes | 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… |
No output schema declared.
No examples provided.
rxnorm_related ~206
Find related medications by RxCUI — brands, generics, ingredients, and dose forms. Maps between brand and generic alternatives. Use to compare drug options.
| Name | Type | Req | Description |
|---|---|---|---|
| rxcui | string | yes | 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,… |
No output schema declared.
No examples provided.
rxnorm_search ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Drug name to search for — brand or generic (e.g., "Ozempic", "semaglutide", "metformin") |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-rxnorm
claude mcp add pipeworx-io-rxnorm -- npx -y @pipeworx/mcp-rxnorm
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.