Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Nih Supplements

NPM · @PIPEWORX/MCP-NIH-SUPPLEMENTS · 2 COMPONENTS

NIH Supplements

+3 this week 83 Trust /100

Last scanned (11 hours ago)

Scores higher than 76% of npm servers

Category Health and Science

Trust breakdown (7 categories)

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-nih-supplements). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 997 tokens (~166/item across 6 items; 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 1 Nov 26 +1

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

  • 30 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 80

    First indexed and scored.

Diagnostics

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-nih-supplements@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-nih-supplements
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-nih-supplements/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3679275273
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:1decab58e1d7f34e02b1143d6216b7f21bd82319692c0d0bf12d7a1c349a7f1b8ac7275e490349c130490dd2459f171d5dd72f835c8034b71890e6389

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~940 tokens

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 →

Tool Tokens
herb_at_a_glance ~184

A popular herb's science-and-safety summary from NIH's National Center for Complementary and Integrative Health (NCCIH) 'Herbs at a Glance' series — what the science says, side effects and cautions, and key references. Covers ~56 widely-used herbs (turmeric, ginkgo, echinacea, garlic, ginseng, milk thistle, St. John's Wort, and more) that NIH's Office of Dietary Supplements does NOT have its own fact sheet for. For a vitamin, mineral, or the handful of botanicals ODS does cover (ashwagandha, black cohosh, valerian), use supplement_factsheet instead.

NameTypeReqDescription
herbstringyesHerb name, e.g. "turmeric" or "St. John's Wort". Fuzzy-matched against the bundled NCCIH herb list.

No output schema declared.

No examples provided.

supplement_factsheet ~225

A specific vitamin, mineral, or supplement's NIH fact sheet — what it does, whether it works, safety, and interactions with medications. Sourced from NIH's Office of Dietary Supplements (ODS). Two reading levels: 'consumer' (short, plain language) or 'professional' (long, clinical, with a references list). Covers ~45 topics (vitamins, minerals, a few botanicals like ashwagandha) — call supplement_factsheets to see the full list. For popular herbs NOT on that list (turmeric, ginkgo, echinacea, garlic, ginseng, milk thistle, St. John's Wort, and more), use herb_at_a_glance instead.

NameTypeReqDescription
levelstring–Reading level. "consumer" (default) is short and plain-language; "professional" is the long clinical version with a references list.
namestringyesTopic name, e.g. "Vitamin D", "Ashwagandha", "Magnesium". Fuzzy-matched against the bundled ODS topic list.

No output schema declared.

No examples provided.

supplement_factsheets ~115

The bundled list of ~45 topics NIH ODS publishes a fact sheet for (vitamins, minerals, a few botanicals) — what to pass as `name` to supplement_factsheet, and which reading levels each has. Optional `query` filters by substring. There is no live NIH endpoint that lists all fact sheets, so this is a point-in-time inventory read from ODS's own list page.

NameTypeReqDescription
querystring–Optional substring filter, e.g. "vitamin" or "iron".

No output schema declared.

No examples provided.

supplement_label ~75

One product's full DSLD label detail: manufacturer contact, every ingredient with its amount, other (non-active) ingredients, and the precaution/warning statements printed on the bottle. Takes the numeric `id` a supplement_labels result returned.

NameTypeReqDescription
idstring|numberyesDSLD label id, from a supplement_labels result.

No output schema declared.

No examples provided.

supplement_labels ~140

Search real supplement product labels — brand name, ingredients, amounts, claims — from NIH's Dietary Supplement Label Database (DSLD). This is what's printed on a bottle, not the science behind an ingredient (use supplement_factsheet or herb_at_a_glance for that). Search by product name, brand, or ingredient. Returns each label's `id` for use with supplement_label.

NameTypeReqDescription
limitnumber–Max labels to return (default 20, max 50).
querystringyesFree-text search — a product name, brand, or ingredient, e.g. "ashwagandha" or "Nature Made fish oil".

No output schema declared.

No examples provided.

supplement_recent_changes ~201

New supplement product labels entered into NIH's Dietary Supplement Label Database (DSLD) since a given date — the one NIH supplement upstream that publishes a queryable change signal. Returns each new label's id, brand, product name, and entry date, newest first; deterministic on replay. Scope is stated, not guessed: DSLD does not publish off-market (withdrawal) transitions as dated events, and neither ODS fact sheets nor NCCIH herb pages publish a queryable list of content-update dates — the response says so explicitly instead of pretending to cover them. Each supplement_factsheet response carries its own 'reviewed' date for direct sweeping.

NameTypeReqDescription
limitnumber–Max new labels to return (default 50, max 200). If more entered since the cutoff, the response sets truncated: true.
sincestringyesCutoff date, YYYY-MM-DD. Labels entered into DSLD on or after this date are returned.

No output schema declared.

No examples provided.

Install

How do I install the Nih Supplements MCP server?

Nih Supplements runs locally as an npm package, launched with npx -y @pipeworx/mcp-nih-supplements. 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-nih-supplements

# add to Claude Code
claude mcp add pipeworx-io-nih-supplements -- npx -y @pipeworx/mcp-nih-supplements
Common questions

What is the Nih Supplements MCP server?

Nih Supplements is an MCP server listed in the public MCP registry as io.github.pipeworx-io/nih-supplements. NIH Supplements. This page covers its npm package (@pipeworx/mcp-nih-supplements).

Is the Nih Supplements MCP server safe to use?

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

Nih Supplements exposes 6 tools: supplement_factsheet, supplement_factsheets, supplement_labels, supplement_label, supplement_recent_changes, herb_at_a_glance. Their descriptions and schemas cost roughly 940 tokens of context every time the server is loaded.

Is the Nih Supplements MCP server still maintained?

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

Nih Supplements 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 Nih Supplements MCP server?

VerifyMCP ran 16 checks on Nih Supplements, 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.