Skip to content
External endpointresponds

Guardian Engine

Deterministic recipe verification engine — validates AI-generated recipes against master SOPs.

Endpoint URL
https://api.kaimeilabs.dev/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
347 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
dev.kaimeilabs/guardian-engine

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
Guardian Engine
Version
1.0.0
Capability keys
experimental, logging, prompts, resources, tools, extensions
Tool names
verify_recipe, fix_recipe, list_dishes, get_master, check_safety, check_allergens, verify_dietary_claim
Instructions excerpt

Guardian Engine is a deterministic recipe verification service. It validates AI-generated recipes against physics-constrained master SOPs using graph-based logic. Guardian always returns a clear Verdict (PASSED/FAILED) and a list of Findings with severity levels. Output is transparent: findings carry exact ingredient names, temperatures, and durations. verify_recipe and fix_recipe return machine-actionable JSON by default; pass response_format='text' for a human-readable report. OPTIONAL — INCLUDE original_prompt: For safety-aware and personalised feedback, include the user's original cooking request in the original_prompt parameter. Copy the user's exact message — do not paraphrase. Example: if the user said 'make me a spicy vegan rendang', pass that exact string. WHY THIS HELPS: - WITHOUT original_prompt: Guardian returns actionable findings with ingredient names and technique hints. - WITH original_prompt: Guardian additionally checks for safety context (e.g., recipes for inf

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 224ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 626ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 447ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 347ms