fact_check_health_claim — Clarity by Health AI MCP Prompt

fact_check_health_claim is one of 3 prompts on the Clarity by Health AI MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke fact_check_health_claim from your client

• Claude Code Clarity by Health AI Prompt/fact_check_health_claim run in your project directory
• Claude Desktop Clarity by Health AI Prompt/fact_check_health_claim ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Clarity by Health AI Prompt/fact_check_health_claim ~/.cursor/mcp.json
• VS Code Clarity by Health AI Prompt/fact_check_health_claim .vscode/mcp.json
• Zed Clarity by Health AI Prompt/fact_check_health_claim ~/.config/zed/settings.json
• Windsurf Clarity by Health AI Prompt/fact_check_health_claim ~/.codeium/windsurf/mcp_config.json
• Cline Clarity by Health AI Prompt/fact_check_health_claim ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Clarity by Health AI Prompt/fact_check_health_claim ~/.gemini/settings.json
• Grok Clarity by Health AI Prompt/fact_check_health_claim .mcp.json (in your project root)
• ChatGPT Clarity by Health AI Prompt/fact_check_health_claim Settings → Connectors → Advanced → Developer mode
• Claude.ai Clarity by Health AI Prompt/fact_check_health_claim Settings → Connectors → Add custom connector
• LangChain Clarity by Health AI Prompt/fact_check_health_claim pip install langchain-mcp-adapters

Other prompts on this server

• audit_supplement_stack
• product_safety_check

Clarity by Health AI also offers 2 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.