validate_and_explain — ibanforge MCP Prompt

validate_and_explain is one of 1 prompt on the ibanforge MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke validate_and_explain from your client

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

ibanforge 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.