Guardian Engine MCP server

What it does

Guardian Engine is a deterministic recipe verification system that validates AI-generated recipes against master standard operating procedures. It catches errors in temperatures, techniques, ingredients, and cooking steps, then returns structured patches for correction. It is built for developers integrating recipe verification into LLM applications.

• Verify that an AI-generated recipe follows your house SOPs and catches hallucinated ingredients, temperatures, or techniques before the recipe is published.
• Check recipes for allergen content, dietary claims (vegan, vegetarian, gluten-free, etc.), and cooking-safety issues with deterministic, auditable results.
• Auto-repair broken recipes by applying structured patches from Guardian's verification findings and re-verify the corrected version.

Tools this server exposes

Tool	Does
list_dishes	List available dishes in the Guardian knowledge base.
verify_recipe	Validate a recipe against master SOPs and return findings, allergen warnings, and structured patches for any violations.
check_allergens	Check a recipe for allergen sources from the automated knowledge base.
verify_dietary_claim	Verify whether a recipe meets a specified dietary claim (vegan, vegetarian, gluten-free, dairy-free, nut-free, halal, kosher) based on ingredient checks.
fix_recipe	Apply structured patches to a recipe to correct violations found during verification.
check_safety	Check a recipe for cooking-safety issues.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.

This server has not seen a commit in 2 mo. It may still work, but nobody is currently fixing it — check the alternatives before you build on it.