Clarity by Health AI
Server Details
Condition-aware ingredient & product safety intelligence for agents: verdict + evidence tier + per-claim evidence_state (cited = ≥1 verified citation / referenced = sourced-but-unverified) + citations, across breastfeeding, pregnancy, histamine/MCAS, rosacea, HS, allergy, fertility, and toddler lenses. Includes validate_claim to fact-check a free-text health claim against curated cited sources.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 9 of 9 tools scored. Lowest: 3.3/5.
Each tool has a clearly distinct purpose: checking single ingredient, interactions, recalls, stacks, alternatives, barcode, product score, strain, and claims. No overlap or ambiguity.
8 out of 9 tools follow the verb_noun pattern (check_*, find_*, scan_*, score_*, validate_*). Only 'strain_lookup' deviates as noun_verb, but it remains clear and readable.
9 tools is well-scoped for a health AI server covering ingredients, interactions, recalls, products, strains, and claims. Each tool earns its place without redundancy.
The tool set covers the full lifecycle: ingredient lookup, interaction checking, recall detection, stack audit, product search/scan, scoring, strain lookup, and claim validation. No obvious gaps for the domain.
Available Tools
9 toolscheck_ingredientInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| lens | No | Single condition lens | all |
| name | Yes | Ingredient name, e.g. 'niacinamide' or 'aged cheddar cheese' | |
| lenses | No | Multiple condition lenses in one call (max 5); wins over `lens` when provided |
check_interactionInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| ingredient_a | Yes | The ingredient to check, e.g. 'iron' or 'calcium' | |
| ingredient_b | No | Optional second ingredient to check a specific pair. Omit to list all interactions for ingredient_a. |
check_recallInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| brand | Yes | Brand or manufacturer name, e.g. 'Nature Made' or 'Similac' | |
| product_name | No | Optional product name to narrow within the brand, e.g. 'infant formula' |
check_stackInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| lens | No | Single condition lens | all |
| lenses | No | Multiple condition lenses in one call (max 5); wins over `lens` when provided | |
| ingredients | Yes | 2-12 ingredient/supplement names, e.g. ['iron','calcium','quercetin'] |
find_alternativesInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| lens | No | Condition lens for the ingredient screen | all |
| count | No | How many alternatives to return (1-5) | |
| barcode | No | UPC/EAN of the product to swap away from (6-14 digits) | |
| product_name | No | Product name to seed from when no barcode is available |
scan_barcodeInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| lens | No | Condition lens | all |
| barcode | Yes | UPC/EAN barcode, 6-14 digits |
score_productInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| lens | No | Condition lens for per-lens fit | |
| barcode | Yes | UPC/EAN barcode, 6-14 digits | |
| category | No | Product category (omit for auto) |
strain_lookupInspect
Look up a cannabis or mushroom species/strain in Clarity's database. Returns verdict, evidence tier, PMID citation, and safety flags.
| Name | Required | Description | Default |
|---|---|---|---|
| species | Yes | Species or strain name, e.g. 'Cannabis sativa' or 'Lion's Mane' |
validate_claimInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| lens | No | Condition lens the claim is about | all |
| statement | Yes | The health/safety claim to validate, e.g. 'niacinamide is safe during pregnancy' |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!