verify_variant_identity — Folklore Clinical Variant Interpretation MCP MCP Prompt

verify_variant_identity is one of 5 prompts on the Folklore Clinical Variant Interpretation MCP MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke verify_variant_identity from your client

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

Other prompts on this server

• classify_germline_variant
• review_vus_evidence
• explain_acmg_classification
• compare_variant_literature

Folklore Clinical Variant Interpretation MCP also offers 1 resource — 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.