Dietary Supplement Analysis (NIH data) MCP server

Dietary Supplement Label and Nutrient Intake Analysis

AI assistants call this service when someone asks "is my supplement routine OK?". Give it the products the way a person names them (product name, barcode or NIH label ID), with age and sex, and optionally their medications, conditions and what they eat. It finds each label in the NIH Dietary Supplement Label Database, totals every vitamin and mineral per day across all of them, and compares the totals with NIH reference intakes and upper limits. It also reports the medication interactions named in the NIH fact sheets, herbs with NIH safety signals, and FDA recalls and adverse event reports. Every answer starts with a plain-language summary an assistant can relay (English or Spanish), and every number traces back to its label or NIH source.

It runs on Pocket Network Beta TestNet as the paid service dietary-supplement-analysis, and as a remote MCP server with a free trial.

Data sources, all public:

• Labels: NIH Dietary Supplement Label Database (DSLD), API v9 plus a weekly mirror of NIH's full download (214,782 labels).
• Reference values: Food and Nutrition Board DRIs, as published on the NIH Office of Dietary Supplements fact sheets.
• Interactions and herbs: NIH ODS and NCCIH fact sheets; medication names are normalized with NIH RxNorm.
• Recalls and adverse events: openFDA.
• Foods: USDA SR28 (FoodData Central "SR Legacy"); typical US intake from What We Eat in America, NHANES 2017–March 2020.

What it is not: medical advice or a diagnosis. It reports what labels declare, compares the totals with published reference values, and relays the interactions and safety statements NIH publishes. The interaction list is not exhaustive, and no flag means nothing was found to report, not an all-clear.

For judges: try it in one minute

Paying agents call the service through Pocket Network: with an application staked for dietary-supplement-analysis on Beta, relay with pocket-ap as shown in Through Pocket Network. The paths and request bodies below are the same either way; the demo endpoint just skips the relay layer so you can use curl without staking.

Shortened. The full README is on GitHub.