Connect Guardian Engine and your agent gets 7 tools, among them check_allergens, check_safety, fix_recipe. It answers at https://api.kaimeilabs.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Deterministic recipe verification engine — validates AI-generated recipes against master SOPs.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 Inputs: ingredients, restrictions, dish_name, check_all_eu_allergens, response_format, session_id |
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 allerge Inputs: candidate_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 Inputs: dish_name, candidate_json, original_prompt, response_format, dish, master_json |
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 loo Inputs: dish_name, response_format |
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 again Inputs: cuisine_filter |
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 verdic Inputs: candidate_json, claim, response_format |
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 a Inputs: dish_name, candidate_json, original_prompt, response_format, session_id, dish |
Every block below points at https://api.kaimeilabs.dev/mcp. Pick your client and copy.
claude mcp add --transport http guardian-engine https://api.kaimeilabs.dev/mcp
{
"mcpServers": {
"guardian-engine": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.kaimeilabs.dev/mcp"]
}
}
}{
"mcpServers": {
"guardian-engine": {
"url": "https://api.kaimeilabs.dev/mcp"
}
}
}{
"servers": {
"guardian-engine": {
"type": "http",
"url": "https://api.kaimeilabs.dev/mcp"
}
}
}{
"context_servers": {
"guardian-engine": {
"url": "https://api.kaimeilabs.dev/mcp"
}
}
}{
"mcpServers": {
"guardian-engine": {
"serverUrl": "https://api.kaimeilabs.dev/mcp"
}
}
}{
"mcpServers": {
"guardian-engine": {
"url": "https://api.kaimeilabs.dev/mcp"
}
}
}name: Guardian Engine
version: 0.0.1
schema: v1
mcpServers:
- name: Guardian Engine
type: streamable-http
url: https://api.kaimeilabs.dev/mcp{
"mcpServers": {
"guardian-engine": {
"httpUrl": "https://api.kaimeilabs.dev/mcp"
}
}
}{
"mcpServers": {
"guardian-engine": {
"type": "http",
"url": "https://api.kaimeilabs.dev/mcp"
}
}
}{
"mcpServers": {
"guardian-engine": {
"url": "https://api.kaimeilabs.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.kaimeilabs.dev%2Fmcp&type=streamable_http&id=guardian-engine&name=Guardian%20Engine
It answered our last check on 19 October 2026 in 128 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by kaimeilabs.dev and served from api.kaimeilabs.dev, the vendor's own domain: https://api.kaimeilabs.dev/mcp.
7, as returned by the server's own tools/list on 11 September 2026: check_allergens, check_safety, fix_recipe, get_master, list_dishes, verify_dietary_claim, verify_recipe.
It answered our last check on 19 October 2026 in 128 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.kaimeilabs.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.kaimeilabs. Endpoint host: api.kaimeilabs.dev. ARD identifier: urn:air:dev.kaimeilabs:mcp:guardian-engine.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.