verify_recipe_prompt — Guardian Engine MCP Prompt

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

by client

How to invoke verify_recipe_prompt from your client

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

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.