Koskamo

Clarity MCP MCP server

An official Model Context Protocol server by Health AI that provides condition-aware ingredient intelligence for AI agents. It allows agents to check ingredients, audit supplement stacks, validate health claims, scan barcodes, and score products against specific health lenses like pregnancy, histamine, or allergies, with verifiable evidence tiers and citations.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Health AI
MCP endpoint (Streamable HTTP)
https://mcp.healthai.com
Vendor documentation

What you can do with it

  • Check ingredient safety for specific conditions like pregnancy or histamine intolerance
  • Audit supplement stacks for curated interactions and per-item verdicts
  • Fact-check free-text health claims against cited scientific sources
  • Scan product barcodes to resolve identity and flag FDA recalls
Tools advertised by the last live check:
  • check_ingredient
  • check_stack
  • find_alternatives
  • strain_lookup
  • scan_barcode
  • validate_claim
  • check_interaction
  • score_product
  • check_recall

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http clarity-mcp https://mcp.healthai.com

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add clarity-mcp --url https://mcp.healthai.com

Cursor

Merge this server into .cursor/mcp.json in your project, then enable clarity-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "clarity-mcp": {
      "url": "https://mcp.healthai.com"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "clarity-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.healthai.com",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start clarity-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "clarity-mcp": {
      "type": "http",
      "url": "https://mcp.healthai.com"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http clarity-mcp https://mcp.healthai.com

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "clarity-mcp": {
      "url": "https://mcp.healthai.com"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "clarity-mcp": {
      "serverUrl": "https://mcp.healthai.com"
    }
  }
}

Do you run Clarity MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing