Guardian Engine
Deterministic recipe verification engine — validates AI-generated recipes against master SOPs.
| Endpoint | https://api.kaimeilabs.dev/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 7 tools · grade C (76) · pin ts_309ce8b82a9002cb87738f01ae30a031 · protocol 2025-06-18 |
| First / last listed | 2026-11-04 03:05 UTC / 2026-11-04 03:05 UTC |
| Grade over time | 2026-11-04: C (76), 7 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: verify_recipe fix_recipe list_dishes get_master check_safety check_allergens verify_dietary_claim
verify_recipe | Verify a candidate recipe against a Guardian master recipe.
Uses deterministic graph-based verification to check technique, temperature,
timing, cooking medium, and required ingredients.
**Verdict**: `verdict` is strictly PASSED or FAILED and is policy-driven — any CRITICAL
finding fails the recipe; more than 5 WARNINGs also fail. There is no score in the
response (ADR-013): gate on `verdict` an params: dish_name, candidate_json, original_prompt, response_format, session_id, dish, operator_id, master_json |
fix_recipe | Deterministically repair a candidate recipe against a Guardian master.
Verifies the candidate, applies every machine-actionable correction the
symbolic engine produced (missing ingredients, quantities, temperatures,
durations, cooking media, ingredient substitutions), then re-verifies the
result. No LLM is used — the repair is a deterministic function of the
candidate recipe and the master rulese params: dish_name, candidate_json, original_prompt, response_format, dish, master_json |
list_dishes | List all available master dishes with rich metadata.
This is a browse/discovery step, not the verification itself — after picking
a dish, call verify_recipe(dish_name=<slug>, candidate_json=<your recipe>) to
actually check a candidate against it (or fix_recipe to auto-repair it).
Returns:
Dictionary with `schema_version`, a `dishes` list (slug, title, cuisine,
region, aliases, complexity params: cuisine_filter |
get_master | Return the canonical master recipe for a dish (read-only, no LLM).
Enables compare-then-verify agentic loops: fetch the master, diff it against the
user's recipe, then call verify_recipe — instead of verifying blind. Pure knowledge-base
lookup, no LLM in the hot path.
Master content is transparent by default (ADR-009 / ADR-010): exact temperatures, timings,
and EU FIC 1169/2011 allergen codes ar params: dish_name, response_format |
check_safety | Run master-independent safety checks on a candidate recipe.
Works for ANY recipe — no dish resolution, no master SOP required. Checks
poultry internal-temperature safety and scans all ingredients for the 14
EU FIC 1169/2011 Annex II allergen groups. The verdict is a deterministic
function of (candidate, kb_version_hash) — no LLM involvement.
Use this when verify_recipe has no matching master for params: candidate_json* |
check_allergens | Check ingredients for EU FIC 1169/2011 allergen compliance.
Returns a detailed audit trace mapping each ingredient to its EU Annex II
allergen group with entry numbers and labels. The safety verdict is
deterministic — no LLM involvement in the decision — and is pinned by the
returned ``kb_version_hash``.
Use check_all_eu_allergens=True for food labelling (detect all allergens).
Use restrictions= params: ingredients*, restrictions, dish_name, check_all_eu_allergens, response_format, session_id, operator_id |
verify_dietary_claim | Verify that a recipe satisfies a dietary claim (vegan, halal, gluten-free, ...).
Reuses the existing allergen-detection logic plus a curated forbidden-ingredient
map (apps/guardian/knowledge/dietary_claims.yaml). Returns a structured verdict
with the specific offending ingredients and a short justification — never a
vague paraphrase. params: candidate_json, claim, response_format |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.