check_entry_handles — Verified Handles MCP Prompt
check_entry_handles
is one of 2 prompts on the
Verified Handles
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke check_entry_handles from your client
- Claude Code Verified Handles Prompt/check_entry_handles run in your project directory
- Claude Desktop Verified Handles Prompt/check_entry_handles ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Verified Handles Prompt/check_entry_handles ~/.cursor/mcp.json
- VS Code Verified Handles Prompt/check_entry_handles .vscode/mcp.json
- Zed Verified Handles Prompt/check_entry_handles ~/.config/zed/settings.json
- Windsurf Verified Handles Prompt/check_entry_handles ~/.codeium/windsurf/mcp_config.json
- Cline Verified Handles Prompt/check_entry_handles ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Verified Handles Prompt/check_entry_handles ~/.gemini/settings.json
- Grok Verified Handles Prompt/check_entry_handles .mcp.json (in your project root)
- ChatGPT Verified Handles Prompt/check_entry_handles Settings → Connectors → Advanced → Developer mode
- Claude.ai Verified Handles Prompt/check_entry_handles Settings → Connectors → Add custom connector
- LangChain Verified Handles Prompt/check_entry_handles pip install langchain-mcp-adapters
Other prompts on this server
Read from the server itself, by connecting to it and calling prompts/list on 8 October 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.