claim_status_check — Trusgent MCP MCP Prompt

claim_status_check is one of 6 prompts on the Trusgent MCP MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke claim_status_check from your client

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

Other prompts on this server

• hk_registry_lookup
• verify_before_recommend
• merged_profile_deep_dive
• business_facade_brief
• ranking_lookup

Trusgent MCP also offers 4 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.