Clarity MCP

What the thehealthai/clarity-mcp MCP server does

thehealthai/clarity-mcp MCP server connects MCP-compatible agents to Clarity’s hosted safety and evidence lookup service. It evaluates ingredients, products, supplement combinations, health claims, cannabis or mushroom strains, and consumer-product recalls against supported condition lenses.

The service can return a condition-specific verdict, an evidence tier, and a citation when available. Supported lenses include breastfeeding, lactation, pregnancy, histamine, MCAS, rosacea, HS, allergy, and all. Each result also includes a human_url pointing to a live Clarity page for the answer.

Tools and capabilities

Thehealthai/clarity-mcp provides nine MCP tools:

• check_ingredient evaluates a cosmetic, food, or supplement ingredient under one or more lenses.
• check_stack reviews supplement items individually and reports curated interactions within the stack.
• find_alternatives ranks same-category alternatives for a flagged product, with quality scoring and lens-based screening. Coverage is explicitly reported, and barcode verification is recommended.
• strain_lookup checks cannabis or mushroom species and strains, including a PMID citation and safety flags.
• scan_barcode identifies a product by UPC or EAN, checks its ingredients against a lens, and surfaces active FDA recalls.
• validate_claim compares a free-text health claim with Clarity’s curated position as supporting, contradicting, or not covered, with a citation.
• check_interaction returns curated ingredient-pair interaction details such as type, severity, mechanism, clinical note, and source.
• score_product produces category-specific food, skincare, or supplement scores by barcode and reports data-quality coverage.
• check_recall searches consumer-product recalls by brand and optional product name, with source URLs and a medical-device scope boundary.

The server also exposes prompts for supplement audits, health-claim fact checks, and product safety checks, plus methodology and lens resources.

How it works

thehealthai/clarity-mcp uses the hosted endpoint https://mcp.healthai.com with Streamable HTTP and JSON-RPC 2.0. Anonymous requests require no installation or API key but are limited to 60 tool calls per minute per IP. An X-API-Key header can be used for higher metered limits.

The service may use Open Food Facts or Open Beauty Facts during barcode lookups to refresh its private product mirror. Calls generate bounded operational telemetry without raw tool arguments. Uncovered claim text may enter a private review queue, so inputs should not contain personal information.

Setup and configuration

Add the remote endpoint to an MCP client as a Streamable HTTP server:

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

Claude Code can register it with claude mcp add --transport http clarity https://mcp.healthai.com. Older clients without native remote MCP support can use the mcp-remote bridge. The endpoint can also be supplied as a remote MCP tool in OpenAI’s Responses API, with approvals enabled during evaluation.

Limitations and notes

thehealthai/clarity-mcp returns descriptive information, not medical advice. A missing flag does not establish that an ingredient or product is safe. Recall searches cover consumer products and explicitly exclude medical-device scope.

Do not send names, contact details, medical records, or other personal information. Requests containing an Origin header must match the MCP endpoint’s origin or receive HTTP 403; non-browser clients may omit that header. The repository documents the hosted service and its client surface, while production implementation, deployment configuration, credentials, and operational data are maintained separately.