
Guardian Engine
Deterministically verify AI-generated operational recipes against your master SOPs before you ship or hand work to operators.
Overview
dev.kaimeilabs/guardian-engine is an MCP server for the Ship phase that deterministically validates AI-generated recipes against master SOPs.
What is this MCP server?
- Guardian Engine remote MCP at api.kaimeilabs.dev/mcp (streamable HTTP)
- Deterministic verification of AI-generated recipes against master SOPs
- Version 1.0.0 hosted service with GitHub docs at kaimeilabs/guardian-api-docs
- Designed as an engine layer, not open-ended LLM self-check
- Hosted MCP version 1.0.0
- Remote URL api.kaimeilabs.dev/mcp
- Documentation repo kaimeilabs/guardian-api-docs on GitHub
What problem does it solve?
Agent-written procedures look plausible but silently diverge from the SOPs your ops team must follow.
Who is it for?
Teams with formal SOPs who want a Kaimei-hosted verification gate on AI-generated operational recipes.
Skip if: Casual scripts with no master SOP baseline or builders who only need informal linting of markdown docs.
What do I get? / Deliverables
Every generated recipe gets a deterministic pass-or-fail against master SOPs inside the agent workflow before release.
- Structured verification results for each AI-generated recipe
- Blocked releases when recipes violate master SOP rules
- Auditable agent workflow hook before operational publish
Recommended MCP Servers
Journey fit
SOP conformance checks are a ship-time gate—after generation, before release—so bad agent output does not reach production runbooks. review is where structured validation of artifacts against standards happens, matching a recipe-vs-SOP engine.
How it compares
Deterministic SOP verification MCP, not a generic code-review skill.
Common Questions / FAQ
Who is dev.kaimeilabs/guardian-engine for?
Builders and operators who publish AI-assisted runbooks or recipes and must match Kaimei master SOPs before deployment.
When should I use dev.kaimeilabs/guardian-engine?
Use it in ship review after an agent drafts a recipe and before you merge, publish, or hand the procedure to production staff.
How do I add dev.kaimeilabs/guardian-engine to my agent?
Connect the remote MCP endpoint https://api.kaimeilabs.dev/mcp in your MCP client and call verification tools per the guardian-api-docs repository.