Hub MCP vs Guardian Engine — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Hub MCP vs Guardian Engine
In-depth architectural comparison of the Hub MCP and Guardian Engine MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Hub MCP
Developer Tools · Remote HTTP/SSE
Quality: 77/100 (Great) | Auth: API Key required
Guardian Engine
Developer Tools · Remote HTTP/SSE
Quality: 41/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Hub MCP if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Guardian Engine if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Hub MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: HUB_PAT_TOKEN, MCP_AUTH_TOKEN.
Hub MCP is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Guardian Engine belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Hub MCP when you need capabilities focused on developer tools and Guardian Engine when you require tools for developer tools.
Number of documents to skip for pagination (number, optional)
images
Filter on image names (string, optional)
operating_systems
Filter on operating systems (string, optional)
order
Change the ordering of results (string, optional)
size
Maximum number of results to return (number, optional)
sort
Sort results by search field (string, optional)
+23 more tools listed on main page
Guardian Engine Tools (7)
verify_recipe
Verify a candidate recipe against a Guardian master spec. Returns a structured report with a strict `PASSED`/`FAILED` verdict (no scores) and detailed findings, each citing the rule it violated. The verdict is policy-driven: any `CRITICAL` finding fails the recipe; more than 5 `WARNING`s also fail.
fix_recipe
Deterministically repair a candidate recipe against a master spec. Verifies, applies every machine-actionable patch the symbolic engine produced (missing ingredients, quantities, temperatures, durations, cooking media, substitutions), then re-verifies. **No LLM is involved** — the repair is a deter…
list_dishes
List all master recipes Guardian can verify against, with rich metadata (slug, title, cuisine, region, aliases, complexity).
get_master
Return the canonical master recipe for a dish — a pure knowledge-base lookup, no LLM. Enables **compare-then-verify** loops: fetch the master, diff it against your recipe, then call `verify_recipe` instead of verifying blind. Master content is transparent by default: exact temperatures, timings, an…
check_safety
Master-independent safety checks for **any** recipe — no dish resolution or master spec required. Checks poultry internal-temperature safety (≥ 74 °C) and scans all ingredients against the 14 EU FIC 1169/2011 Annex II allergen groups. Use it when `verify_recipe` has no matching master.
check_allergens
Check an ingredient list for EU FIC 1169/2011 allergen presence, with a detailed audit trace mapping each ingredient to its Annex II allergen group (entry numbers and labels included).
verify_dietary_claim
Verify that a recipe satisfies a dietary claim, returning a structured verdict with the specific offending ingredients — never a vague paraphrase.