mcp server
Clarity by Health AI
Condition-aware ingredient and product checks for agents, with evidence tiers and citations.
Description as published by the maintainer. Source
- version 0.7.8
- archived
archived — The linked repository returns 404. It was deleted, renamed or made private.
What this server can do
9 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_ingredient(lens, name, lenses)- Look up a cosmetic/food/supplement ingredient in Clarity's condition-aware database. Returns verdict, evidence tier (Gold/Silver/Bronze), and citation for a given condition lens. Pass `lenses` (array) instead of `lens` to check several conditions in ONE call (profile-shaped checking, e.g. a user who is pregnant AND has MCAS) — results then carry a per-lens breakdown under `lenses{}`. Every result includes human_url, a live Clarity page to hand the user as the source link. Required: name.
check_interaction(ingredient_a, ingredient_b)- Check Clarity's curated ingredient-to-ingredient interaction database. Give one ingredient to list everything it interacts with (e.g. 'iron'), or two ingredients to check a specific pair (e.g. 'calcium' + 'iron'). Returns interaction_type, severity (Beneficial/Moderate/High), mechanism, clinical_note, source, and whether it affects lactation/infant/absorption. Queries both directions of the pair. Absence of a result is NOT proof of safety — the set is curated and growing. Descriptive with sources, not medical advice. Required: ingredient_a.
check_recall(brand, product_name)- Check whether a consumer product or brand has an FDA/consumer recall on file — supplements, food, cosmetics (NOT medical devices). Query by `brand` (primary), optionally narrow by `product_name`. Returns recall_flag, whether any active Class I (most serious) recall exists, and each matching record with classification, reason, date, status, and a source_url to verify. Recall data has no barcode, so matches are brand/name text matches — confirm via source_url. For medical-DEVICE recalls, use the radar MCP (com.healthai/radar). Required: brand.
check_stack(lens, lenses, ingredients)- Audit a supplement/ingredient STACK in one call: per-item condition-lens verdicts (evidence-graded, cited where citations exist) PLUS every curated ingredient-to-ingredient interaction found WITHIN the stack (type, severity, mechanism, source). Use when a user takes multiple supplements together. Supports multi-lens via `lenses`. Absence of an interaction is NOT proof of safety — the curated set is growing. Every result includes human_url for the user. Required: ingredients.
find_alternatives(lens, count, barcode, product_name)- Find 2-3 safer swaps for a flagged product: same-category products that rate good/excellent on Clarity's general food/skincare quality score AND contain no ingredient flagged for the given condition lens. Seed by barcode (preferred — e.g. right after scan_barcode flags something) or product_name. Each alternative carries its score, ingredient-recognition coverage, and human_url. The score is a GENERAL quality score, not a condition verdict — verify a chosen alternative with scan_barcode or check_stack. Food and skincare only (supplement swaps are declined honestly for now).
scan_barcode(lens, barcode, persist_mirror, harvest_crosswalk)- Look up a product by barcode (Open Food Facts / Open Beauty Facts), match its ingredients against Clarity's database, return which ingredients are flagged for the given condition lens, AND flag any active FDA recall for the product (recall_flag + recalls[], sourced from FDA — verify via source_url). Anonymous calls are read-only: a local-mirror miss may query the public source but does not refresh Clarity's mirror or harvest tokens. An authenticated caller may opt into each bounded side effect with persist_mirror:true and harvest_crosswalk:true. Required: barcode.
score_product(lens, barcode, category)- Get Clarity's product quality score by barcode. Returns category-specific scores (food: nutrition/additive/processing/organic; skincare: irritation/allergen/endocrine/condition; supplement: transparency/safety/label_quality/complexity — dose transparency penalizes proprietary blends, safety flags high-risk botanicals) — these are DISTINCT and never merged — plus per-lens fit with match coverage. Always includes data_quality/coverage so a score is never given without its confidence. Required: barcode.
strain_lookup(species)- Look up a cannabis or mushroom species/strain in Clarity's database. Returns verdict, evidence tier, PMID citation, and safety flags. Required: species.
validate_claim(lens, statement, review_consent)- Fact-check a free-text health/safety claim against Clarity's human-curated, evidence-graded database. Given a statement (e.g. 'fenugreek is safe while breastfeeding') and a condition lens, returns whether Clarity's curated position supports / contradicts / does-not-cover it, plus any verified citation on file. Anonymous calls never write the review queue. An authenticated caller may explicitly opt into a bounded, redacted review signal with review_consent:true. Do not include personal information. Descriptive — not medical advice. Required: statement.
Last successful function declaration observed on . Source: https://mcp.healthai.com. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.healthai.com.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.7.8 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-30 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-30 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | not_found | GitHub returned 404 for the repository the maintainer listed. The project was deleted, renamed or made private, so the listing points at nothing. | as of fetch | GitHub | |
| mcp tools declared | 9 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.healthai.com | |
| mcp endpoint status | ok | The server listed 9 functions when asked. | as of probe | mcp.healthai.com |
Where to get it
Also from healthai-hq
-
Constat MCP — FDA Device Evidence Lifecycle
— repository gone
FDA and CMS evidence for AI medical devices: 510(k), postmarket, reimbursement, and compliance.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json