Dailymed
NPM · @PIPEWORX/MCP-DAILYMED · 2 COMPONENTS
DailyMed MCP — FDA Structured Product Labels via NLM
Available components
Last scanned (2 hours ago)
Scores higher than 72% 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-dailymed). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1215 tokens (~173/item across 7 items; 7 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 Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 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 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 79
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-dailymed@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-dailymed |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-dailymed/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612334512 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4e78ff345404cde10bb4c2310efc2e0f7678801e0c00efc21d63b58214a7591419c75f73ce5173c1465db11e6ef27bd8a60b4452325fb29907e4532c4 |
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 →
get_drug ~279
FULL FDA DRUG LABEL TEXT from the current DailyMed Structured Product Label — indications, dosage and administration, contraindications, warnings and precautions, boxed warning, adverse reactions, and every other labeled section, as readable plain text. Pass a DRUG NAME ("Ozempic", "ibuprofen") and it resolves the label automatically, or a DailyMed set_id. PREFER OVER WEB SEARCH for "what are the warnings for X", "what is X indicated for", "what is the dose of X", "does X have a boxed warning". Returns the label title, labeler, SPL version and publication date alongside the sections.
| Name | Type | Req | Description |
|---|---|---|---|
| drug_name | string | – | Drug brand or generic name (e.g. "Ozempic", "ibuprofen"). Resolved to the primary manufacturer's label. Use this OR set_id. |
| max_section_chars | number | – | Truncate each section body to this many characters (default 4000, max 40000). |
| section | string | – | Optional case-insensitive substring filter, matched against both the section heading and its LOINC category, e.g. "boxed warning", "warnings", "dosage", "indications". Omit for the whole label. |
| set_id | string | – | DailyMed SET ID UUID, when you already have one. Takes precedence over drug_name. |
No output schema declared.
No examples provided.
label_diff ~267
WHAT CHANGED between two versions of a drug's FDA label — conservative section-level text comparison of official DailyMed SPL versions. Pass a DRUG NAME ("Ozempic") and it resolves the label automatically; or pass a set_id. Defaults to the latest version versus its immediate predecessor. PREFER OVER WEB SEARCH for "what changed in X's label", "new warnings added to X", "did X get a boxed warning", label-change diffing. Reports added, removed, and changed sections with normalized before/after text. Reports textual change only and leaves clinical materiality to the caller.
| Name | Type | Req | Description |
|---|---|---|---|
| drug_name | string | – | Drug brand or generic name (e.g. "Ozempic"). Resolved to the primary manufacturer's label. Use this OR set_id. |
| from_version | number | – | Older SPL version. Defaults to the version immediately before the latest. |
| include_unchanged | boolean | – | Include unchanged sections (default false). |
| max_sections | number | – | Maximum section records returned (1-100, default 25); counts cover all sections. |
| set_id | string | – | DailyMed SET ID UUID, when you already have one. Takes precedence over drug_name. |
| to_version | number | – | Newer SPL version. Defaults to the latest version. |
No output schema declared.
No examples provided.
label_history ~226
Drug LABEL REVISION HISTORY — when a prescription drug's FDA label was revised, and how many times. Pass a DRUG NAME ("Ozempic", "semaglutide") and it resolves to that drug's Structured Product Label automatically; or pass a DailyMed set_id directly. PREFER OVER WEB SEARCH for "has the label for X changed recently", "when was X's label last updated", "how many label revisions does X have", label-change monitoring, and safety-labeling-change surveillance. Returns every published SPL version with its date, plus official archive URLs where DailyMed exposes them. Use before label_diff to see which versions are downloadable and pick two to compare.
| Name | Type | Req | Description |
|---|---|---|---|
| drug_name | string | – | Drug brand or generic name (e.g. "Ozempic", "semaglutide"). Resolved to the primary manufacturer's label (the most-revised SPL for that name, over repackager duplicates). Use this OR set_id. |
| set_id | string | – | DailyMed SET ID UUID, when you already have one. Takes precedence over drug_name. |
No output schema declared.
No examples provided.
list_classes ~154
List pharmacologic drug-class reference entries from DailyMed, optionally filtered by class_code or class type (EPC = established pharmacologic class, MoA = mechanism of action, PE = physiologic effect, CS = chemical structure). Returns class codes and display names. ~1,210 classes total, 100 per page.
| Name | Type | Req | Description |
|---|---|---|---|
| class_code | string | – | Restrict to a specific class code. NLM RxClass format, e.g. "N0000175809" — not a UMLS CUI. |
| page | number | – | 1-based page (100 per page, ~13 pages). Ignored when class_code is given. |
| type | string | – | EPC | MoA | PE | CS |
No output schema declared.
No examples provided.
list_labels_for_drug_name ~42
All labels mentioning a drug name.
| Name | Type | Req | Description |
|---|---|---|---|
| drug_name | string | yes | – |
| page | number | – | – |
| pagesize | number | – | – |
No output schema declared.
No examples provided.
recent_updates ~59
Return the most recently updated FDA Structured Product Labels from DailyMed (NLM), up to 100 results, ordered by update date descending. Useful for tracking newly revised drug labeling.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 1-100 (default 25) |
No output schema declared.
No examples provided.
search_drugs ~134
Search Structured Product Labels by any combination of name, ANDA/NDA, NDC, RxCUI.
| Name | Type | Req | Description |
|---|---|---|---|
| application_number | string | – | ANDA/NDA number (e.g. "NDA021436") |
| manufacturer | string | – | Manufacturer name |
| name | string | – | Drug name (brand or generic) |
| ndc | string | – | NDC code (11-digit) |
| page | number | – | 1-based page (default 1) |
| pagesize | number | – | 1-100 (default 25) |
| rxcui | string | – | RxNorm RxCUI |
No output schema declared.
No examples provided.
How do I install the Dailymed MCP server?
Dailymed runs locally as an npm package, launched with npx -y @pipeworx/mcp-dailymed. 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-dailymed
claude mcp add pipeworx-io-dailymed -- npx -y @pipeworx/mcp-dailymed
What is the Dailymed MCP server?
Dailymed is an MCP server listed in the public MCP registry as io.github.pipeworx-io/dailymed. DailyMed MCP, FDA Structured Product Labels via NLM. This page covers its npm package (@pipeworx/mcp-dailymed).
Is the Dailymed MCP server safe to use?
Dailymed 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 Dailymed MCP server expose?
Dailymed exposes 7 tools: search_drugs, get_drug, list_labels_for_drug_name, recent_updates, label_history, and 2 more. Their descriptions and schemas cost roughly 1,161 tokens of context every time the server is loaded.
Is the Dailymed MCP server still maintained?
Dailymed 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 Dailymed MCP server under?
Dailymed declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.