Lifestyle · Official remote MCP server

The Guardian Engine MCP server,
connected in one click.

Deterministic recipe verification engine — validates AI-generated recipes against master SOPs. Connect the official Guardian Engine MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.

Connect Guardian Engine free How it works

Free to start · No credit card · No hosting needed

Use this server

Add Guardian Engine to your AI in one minute

Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.

claude mcp add --transport http guardian-engine https://api.kaimeilabs.dev/mcp

Run in your terminal, then restart Claude Code.

Guardian Engine · https://api.kaimeilabs.dev/mcp

What you can do

What your AI can do with Guardian Engine

Real prompts you can type the moment it's connected — no setup, no docs to read.

“Use “verify_recipe”: Verify a candidate recipe against a Guardian master recipe. Uses deterministic graph-based verification to check technique, temperature, ti.”

“Use “fix_recipe”: Deterministically repair a candidate recipe against a Guardian master. Verifies the candidate, applies every machine-actionable correction.”

“Use “list_dishes”: List all available master dishes with rich metadata. This is a browse/discovery step, not the verification itself — after picking a dish, c.”

“Use “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 aga.”

Security check

How secure is the Guardian Engine MCP server?

Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Guardian Engine holds up.

✓ Verified directory serverGuardian Engine · kaimeilabs.dev

Official endpoint

Operated by Guardian Engine (kaimeilabs.dev) at its documented MCP endpoint — not a third-party mirror or community re-host.

No sign-in needed

This server only exposes public data — no account and no credentials are involved when you connect.

Scanned before it goes live

gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.

Watched for drift

If Guardian Engine adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.

Run the free scanner on Guardian Engine's server →

How it works

Connected in three steps

Connect your gate

Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.

Pick Guardian Engine

Choose Guardian Engine in the gate directory. No sign-in needed.

Use it anywhere

Guardian Engine's tools are live in every AI client you've connected — with rules and logging built in.

Connect Guardian Engine free

Free to start · No credit card · No hosting needed

Straight from the server

The actual tools Guardian Engine exposes

Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.

verify_recipe — Verify a candidate recipe against a Guardian master recipe. Uses deterministic graph-based verification to check technique, temperature, ti

fix_recipe — Deterministically repair a candidate recipe against a Guardian master. Verifies the candidate, applies every machine-actionable correction

list_dishes — List all available master dishes with rich metadata. This is a browse/discovery step, not the verification itself — after picking a dish, c

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 aga

check_safety — Run master-independent safety checks on a candidate recipe. Works for ANY recipe — no dish resolution, no master SOP required. Checks poult

check_allergens — Check ingredients for EU FIC 1169/2011 allergen compliance. Returns a detailed audit trace mapping each ingredient to its EU Annex II aller

verify_dietary_claim — Verify that a recipe satisfies a dietary claim (vegan, halal, gluten-free, ...). Reuses the existing allergen-detection logic plus a curate

Author

Who runs the Guardian Engine MCP server?

kaimeilabs.dev

More servers from kaimeilabs.dev →

Own this server? Claim the listing →

Server facts

The Guardian Engine MCP server at a glance

Endpointhttps://api.kaimeilabs.dev/mcp

Operated byGuardian Engine (kaimeilabs.dev)

CategoryLifestyle

Sign-inNone — public data only

Available in gateYes — one-click connect

Works withClaude, ChatGPT, Cursor & any MCP client

FAQ

Questions, answered

Is there an official Guardian Engine MCP server?

Yes — Guardian Engine operates its own remote MCP server at api.kaimeilabs.dev. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.

How do I connect Guardian Engine to Claude or ChatGPT?

Add gate's gateway URL to your AI client once, then pick Guardian Engine in the directory. No account or sign-in is needed. From then on, Guardian Engine's tools are available in every client you've connected to gate.

Do I need to host anything?

No. Guardian Engine runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.

Is the Guardian Engine MCP server safe to connect?

It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.