Data · Remote MCP server
Clarity by Health AI
Condition-aware ingredient and product checks for agents, with evidence tiers and citations.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.healthai/clarity- Version
- 0.7.8
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-07-30
- Updated
- 2026-07-30
- Publisher
- com.healthai · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain healthai.com · how
- Website
- healthai.com/clarity/api/
- Repository
- github.com/healthai-hq/clarity-project (folder workers/clarity-mcp)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.healthai.com | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- clarity-mcp 0.7.8 · protocol 2025-06-18
- Tools discovered
- 9:
check_ingredient,check_stack,find_alternatives,strain_lookup,scan_barcode,validate_claim,check_interaction,score_product,check_recall - Checked on
- 2026-10-05
How to connect Clarity by Health AI
Clarity by Health AI is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.healthai.com, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.healthai
| Server | Runs |
|---|---|
| Constat MCP - FDA Device Evidence LifecycleFDA and CMS evidence for AI medical devices: 510(k), postmarket, reimbursement, and compliance. | Remote · HTTPLive check: ✓ handshake |
More data servers
| Server | Runs |
|---|---|
| ClaimHitFind products & standards using a patent - verified targets for licensing or enforcement. | Remote · HTTPLive check: ✓ handshake |
| Clara - Personal Clean Air PlannerUK personal air quality advice and daily exposure assessment. Pairs with Hermes for live data. | Remote · HTTPLive check: ✓ handshake |
| ClarigridRead-only electricity, gas, and weather data with structured provenance and units. | Remote · HTTPLive check: sign-in required |
| ClariLayerIndividual-analyst context layer: recall, remember, and reconcile your data and engineering context. | Remote · HTTPLive check: sign-in required |
| classifier.dev docsClassifier.dev documentation as tools: list, read and search the reference, benchmark and guides. | Remote · HTTPLive check: ✓ handshake |
| Claude Ops Telegram ServerTelegram personal-account MCP (MTProto user-auth). Read DMs, send messages, search across chats. | Local · stdio |
| Claudeers MCP ServerSearch the Claudeers registry of Claude tools, ranked by maintenance and community signals. | Remote · HTTPLive check: ✓ handshake |
| ClaudeInk - Knowledge VaultSave, search, and compile valuable knowledge from your Claude conversations. | Local · stdio |