Guardian Engine
Guardian Engine is an MCP server published by kaimeilabs.dev, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-25.
Does Guardian Engine support the current MCP specification (2026-07-28)?
Not yet confirmed. Guardian Engine is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.
Is Guardian Engine a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Guardian Engine (as of 2026-08-25).
How do I connect to Guardian Engine?
Guardian Engine is available via a hosted remote endpoint at https://api.kaimeilabs.dev/mcp, the official MCP Registry under dev.kaimeilabs/guardian-engine, the source repository at https://github.com/kaimeilabs/guardian-api-docs. Authentication: none. Transports: sse-legacy.
What tools does Guardian Engine expose?
Guardian Engine exposes 7 tools, including verify_recipe, fix_recipe, list_dishes, get_master, check_safety, check_allergens (last verified 2026-08-25).
Does Guardian Engine support MCP revision 2025-11-25?
Yes. Guardian Engine supports MCP revision 2025-11-25 (checked 2026-08-25).
When were Guardian Engine's facts last verified?
2026-08-25. Each fact on this page links to the sources used to verify it.
Which tools does Guardian Engine expose?
7 tools verified.
verify_recipefix_recipelist_dishesget_mastercheck_safetycheck_allergensverify_dietary_claim
Deterministic recipe verification engine - validates AI-generated recipes against master SOPs.
Which MCP spec revisions does Guardian Engine support?
Guardian Engine has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source |
How widely adopted is Guardian Engine?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for Guardian Engine
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 0
- Forks
- 0
- Last pushed
- (74 days ago)
- Created
- Open issues
- 0
- Primary language
- Python
- License (repository)
- MIT
- Continuous integration
- None detected
- Tests
- None detected
- Security policy
- None
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.85 (Good).
- Official MCP Registry record for dev.kaimeilabs/guardian-engine at version 1.0.0 - lists remote endpoint https://api.kaimeilabs.dev/mcp and repository https://github.com/kaimeilabs/guardian-api-docs - accessed
- Endpoint probe of https://api.kaimeilabs.dev/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 7 tools - accessed
- Endpoint probe of https://api.kaimeilabs.dev/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 7 tools - accessed