Skip to main content
Glama

Clarity MCP — com.healthai/clarity

Clarity is a condition-aware ingredient checker and scanner for wellness, fitness, tracker, and health-AI workflows. Results can include a verdict, an evidence tier (Gold/Silver/Bronze), and citations when available.

Hosted MCP server — no install and no key required for anonymous, rate-limited access. Endpoint: https://mcp.healthai.com (Streamable HTTP, JSON-RPC 2.0). Published to the official MCP Registry as com.healthai/clarity (domain-verified namespace).

For a human-readable implementation guide covering Claude.ai, Claude Code, OpenAI's Responses API, generic remote MCP configuration, tool boundaries, and the MCP-versus-REST decision, see healthai.com/clarity/mcp.

Use it

Claude Code:

claude mcp add --transport http clarity https://mcp.healthai.com

Claude Desktop / Cursor / any client with native remote MCP — add to the config's mcpServers:

{
  "mcpServers": {
    "clarity": {
      "type": "streamable-http",
      "url": "https://mcp.healthai.com"
    }
  }
}

For older clients without native remote support, bridge with mcp-remote: "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.healthai.com"].

OpenAI Responses API: pass the hosted endpoint as a remote MCP tool and keep approvals enabled while evaluating it:

import OpenAI from "openai";

const client = new OpenAI();
const response = await client.responses.create({
  model: "gpt-5.6",
  tools: [{
    type: "mcp",
    server_label: "clarity",
    server_url: "https://mcp.healthai.com",
    require_approval: "always"
  }],
  input: "Audit iron, calcium, and magnesium for pregnancy and interactions."
});

Related MCP server: citedhealth-mcp

Tools (9)

Tool

What it answers

check_ingredient

Verdict + evidence tier + citation for a cosmetic/food/supplement ingredient, under one condition lens or several at once (lenses: [..])

check_stack

Audit a supplement stack in one call: per-item condition verdicts plus every curated interaction within the stack

find_alternatives

Safer same-category swaps for a flagged product — general quality-score ranked, lens-flag screened, coverage-honest (food/skincare; verify the pick with scan_barcode)

strain_lookup

Verdict, tier, PMID citation and safety flags for a cannabis or mushroom species/strain

scan_barcode

Look up a product by UPC/EAN, flag its ingredients for a condition lens, and surface any active FDA recall

validate_claim

Fact-check a free-text health claim against Clarity's curated position — supports / contradicts / does-not-cover, with citation

check_interaction

Curated ingredient-to-ingredient interactions — type, severity, mechanism, clinical note, source (single or pair)

score_product

Category-specific product quality score by barcode (food / skincare / supplement), each dimension distinct, always with data-quality coverage

check_recall

Consumer-product recall matches by brand and optional product name, with source URLs and a medical-device scope boundary

Condition lenses: breastfeeding, lactation, pregnancy, histamine, mcas, rosacea, hs, allergy, all.

Every result includes human_url — a live Clarity page for that exact answer (gated against the site's keep-list so it never 410s), for agents to hand their user as the source link. The server also exposes MCP prompts (audit_supplement_stack, fact_check_health_claim, product_safety_check) and resources (clarity://methodology, clarity://lenses).

Anonymous use is rate-limited to 60 tool calls/min per IP (Durable Object limiter); add an X-API-Key header for higher metered limits. The scan_barcode live fallback can refresh Clarity's product mirror and count unmatched ingredient tokens. Uncovered validate_claim statements can be counted in the review queue, so inputs must not contain personal information. Descriptive — not medical advice; absence of a flag is not proof of safety.

For MCP transport security, non-browser clients may omit Origin. Requests to the MCP endpoint that include Origin must match the requested endpoint's origin exactly; mismatches return HTTP 403.

Data handling

Tool inputs can include ingredient or product names, condition lenses, supplement stacks, barcodes, ingredient pairs, and free-text health claims. Every tool call writes bounded operational telemetry for reliability, abuse prevention, and latency monitoring. That telemetry includes the tool name, keyed/anonymous status, condition lens, a short request fingerprint, status, and duration; it does not include raw tool arguments. scan_barcode may query Open Food Facts or Open Beauty Facts and refresh a private Clarity mirror. Uncovered validate_claim text may enter a private review queue.

Do not send names, contact details, medical records, or other personal information. Review the public privacy policy before connecting this server.

Runnable direct, LangChain, LlamaIndex, Cloudflare Agents, and Hugging Face client examples live in examples/mcp.

This repository is the curated public developer surface for the hosted server: setup, examples, metadata, and the stdio bridge. Production implementation, deployment configuration, credentials, and operational data are maintained separately.

Available Tools

9 tools
check_ingredientAInspect

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.

Inputs: name (required), lens, lenses.

check_interactionAInspect

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.

Inputs: ingredient_a (required), ingredient_b.

check_recallAInspect

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).

Inputs: brand (required), product_name.

check_stackAInspect

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.

Inputs: ingredients (required), lens, lenses.

find_alternativesAInspect

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).

Inputs: lens, count, barcode, product_name.

scan_barcodeAInspect

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).

Inputs: barcode (required), lens.

score_productAInspect

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.

Inputs: barcode (required), lens, category.

strain_lookupAInspect

Look up a cannabis or mushroom species/strain in Clarity's database. Returns verdict, evidence tier, PMID citation, and safety flags.

Inputs: species (required).

validate_claimAInspect

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. Use this to check whether a health claim an agent already holds aligns with Clarity's curation. Descriptive — not medical advice.

Inputs: statement (required), lens.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: strain lookup, ingredient check, stack audit, alternatives finder, barcode scan, claim validation, interaction check, product scoring, and recall check. No two tools overlap significantly in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_ingredient, scan_barcode). The verbs vary but are appropriate to each action, and no mixing of naming conventions occurs.

    Tool Count5/5

    9 tools is well within the ideal range (3-15). Each tool serves a specific query need for the Clarity database, covering strains, ingredients, stacks, barcodes, claims, interactions, scoring, and recalls without excess.

    Completeness5/5

    The tool set covers the full range of expected queries for a product/ingredient safety database: lookups by strain, ingredient, barcode, stack, claim verification, interaction checks, product scoring, and recall checks. There are no obvious missing operations for a read-only informational MCP server.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for CITED Health that allows AI assistants to query evidence-based supplement data, including ingredient evidence grades, health conditions, PubMed papers, glossary terms, and educational guides.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      The MCP server behind Constat — FDA & NHTSA regulatory-risk intelligence for AI agents, over the Model Context Protocol. Live public regulatory data — recalls, adverse events, warning letters, 510(k) premarket evidence, postmarket drift signals, reimbursement pathways, and vehicle safety. Decision support, not regulatory advice.
      14
      MIT