dev.kaimeilabs/guardian-engine

Est-ce que dev.kaimeilabs/guardian-engine est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.kaimeilabs/guardian-engine » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 7 outils

• check_allergens≈ 685 tokens

  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 the decision — and is pinned by the returned ``kb_version_hash``. Use check_all_eu_allergens=True for food labelling (detect all allergens). Use restrictions=['dairy', 'gluten'] to check for specific user allergies. Supplying neither runs the full 14-group Annex II scan and sets ``defaulted_to_full_scan`` — the tool never reports "safe" without checking. ``is_safe`` answers "was a supplied restriction violated?"; ``declared_allergens`` answers "what is actually present?". Read both.

  Paramètres, retour & exemple (7)

  Paramètres

  • dish_name · ? · optionnel
    Optional dish name for reporting context.
  • session_id · ? · optionnel
    Optional session identifier so repeated checks are stitched into one trajectory.
  • ingredients · array · requis
    List of ingredient names (freeform or canonical IDs). Examples: ['butter', 'wheat_flour', 'eggs', 'peanut_butter']
  • operator_id · ? · optionnel
    Optional audit identifier for the calling operator (letters, digits, hyphens; max 64 chars). Tags the check in the telemetry log. Defaults to 'anonymous'.
  • restrictions · ? · optionnel
    Allergen group IDs to check against user restrictions. Valid IDs: gluten, crustaceans, eggs, fish, peanuts, soy, dairy, tree_nuts, celery, mustard, sesame, sulphites, lupin, molluscs. If None and check_all_eu_allergens=True, reports all detected allergens.
  • response_format · string · optionnel
    Response format: 'json' (default) for the machine-actionable payload, or 'text' for a human-readable report.
  • check_all_eu_allergens · boolean · optionnel
    If True, scans for all 14 EU Annex II allergens regardless of restrictions list. Use this for food labelling (declare all allergens present).

  Exemple d'appel

  {"name": "check_allergens", "arguments": {"ingredients": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}

• check_safety≈ 274 tokens

  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 allergen groups. The verdict is a deterministic function of (candidate, kb_version_hash) — no LLM involvement. Use this when verify_recipe has no matching master for the dish: the safety layer still applies to every recipe. Returns: Safety envelope: verdict (PASSED/FAILED per the zero-critical policy gate), safe flag, issues found, and the pinned kb_version_hash.

  Paramètres, retour & exemple (1)

  Paramètres

  • candidate_json · string · requis
    The full candidate recipe as a JSON string. Checked for poultry internal temperature safety (≥74°C) and EU FIC 1169 allergen presence.

  Exemple d'appel

  {"name": "check_safety", "arguments": {"candidate_json": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• fix_recipe≈ 717 tokens

  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, ingredient substitutions), then re-verifies the result. No LLM is used — the repair is a deterministic function of the candidate recipe and the master ruleset. Findings that need recipe-authoring judgement — adding a whole cooking phase, rewriting step instructions, ingredient-ratio rebalancing — are not auto-applied; they are returned under `patches_skipped`. Allergen findings are never auto-fixed. The response reports the verdict before and after so the caller can see exactly what was resolved. Note: `verdict_after` may still be FAILED when structural changes (e.g. adding a cooking step, rebalancing ingredient ratios) are needed. These require recipe-authoring judgement and are returned under `patches_skipped`. Callers should NOT assume a fixed recipe will pass verification.

  Paramètres, retour & exemple (6)

  Paramètres

  • dish · ? · optionnel
    Alias for dish_name — for backward compatibility with production clients.
  • dish_name · string · optionnel
    Name of the dish to repair against (e.g. 'carbonara', 'rendang', 'roast-chicken'). Use list_dishes() to see all available recipes and their aliases.
  • master_json · ? · optionnel
    Optional user-supplied master SOP to repair against (BYO master, ADR-018), same schema as catalog masters. When provided, the catalog is bypassed and dish_name may be omitted; patches (including suggested_step templates) are built from THIS spec.
  • candidate_json · ? · optionnel
    The full candidate recipe as a JSON string or object — same schema as verify_recipe's candidate_json (title, cuisine, ingredients[], steps[]).
  • original_prompt · ? · optionnel
    Optional. The user's original cooking request, used only for safety-context awareness during verification. Does not change which fixes are applied.
  • response_format · string · optionnel
    Response format: 'json' (default — includes the full fixed_recipe object) or 'text' (human-readable report).

  Exemple d'appel

  {"name": "fix_recipe", "arguments": {"dish": "texte", "dish_name": "texte", "master_json": "texte", "candidate_json": "texte", "original_prompt": "texte", "response_format": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}

• get_master≈ 366 tokens

  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 lookup, no LLM in the hot path. Master content is transparent by default (ADR-009 / ADR-010): exact temperatures, timings, and EU FIC 1169/2011 allergen codes are returned verbatim, never obfuscated. No score is included (ADR-013) — this is reference data, not a verdict. Returns ingredients, steps (technique/temperature/timing/medium), and the EU FIC allergens derived from the required ingredients. Unknown dishes return a structured UNKNOWN_DISH error.

  Paramètres, retour & exemple (2)

  Paramètres

  • dish_name · string · optionnel
    Name or alias of the dish to fetch the canonical master recipe for (e.g. 'carbonara', 'spaghetti bolognese', 'angel food cake'). Alias resolution and slug normalisation are applied. Use list_dishes() to browse.
  • response_format · string · optionnel
    Response format: 'json' (default, structured) or 'text' (human-readable summary).

  Exemple d'appel

  {"name": "get_master", "arguments": {"dish_name": "texte", "response_format": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}

• list_dishes≈ 282 tokens

  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 against it (or fix_recipe to auto-repair it). Returns: Dictionary with `schema_version`, a `dishes` list (slug, title, cuisine, region, aliases, complexity per dish), and a `next_step` hint describing how to proceed to verification.

  Paramètres, retour & exemple (1)

  Paramètres

  • cuisine_filter · string · optionnel
    Optional cuisine to filter by. Case-insensitive exact match against the dish's cuisine field. Valid values: italian | french | spanish | british | thai | chinese | indian | indonesian | japanese | malaysian | korean | mexican | american | moroccan | turkish | levantine. Leave empty to return all available dishes.

  Exemple d'appel

  {"name": "list_dishes", "arguments": {"cuisine_filter": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_dietary_claim≈ 318 tokens

  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 verdict with the specific offending ingredients and a short justification — never a vague paraphrase.

  Paramètres, retour & exemple (3)

  Paramètres

  • claim · string · optionnel
    Dietary claim to verify: vegan | vegetarian | gluten_free | dairy_free | nut_free | halal | kosher.
  • candidate_json · string · optionnel
    Recipe JSON string (CandidateRecipe schema). Expected shape: {"title": "...", "ingredients": [{"name": "..."}, ...], "steps": [...]}. Only the ingredient list is required for dietary verification.
  • response_format · string · optionnel
    Response format: 'text' (default, human-readable) or 'json' (machine-actionable).

  Exemple d'appel

  {"name": "verify_dietary_claim", "arguments": {"claim": "texte", "candidate_json": "texte", "response_format": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}

• verify_recipe≈ 1080 tokens

  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 and is policy-driven — any CRITICAL finding fails the recipe; more than 5 WARNINGs also fail. There is no score in the response (ADR-013): gate on `verdict` and explain failures from `findings`. **Field audience**: `issue` is a machine-readable code for programmatic handling — never show it to end users. Use `title` and `suggested_correction` as the user-facing fields. Returns structured JSON by default (machine-actionable findings and patches); response_format="text" renders a human-readable report. Both formats are transparent (ADR-009 / ADR-018): exact values and ingredient names included.

  Paramètres, retour & exemple (8)

  Paramètres

  • dish · ? · optionnel
    Alias for dish_name — for backward compatibility with production clients.
  • dish_name · string · optionnel
    Name of the dish to verify against (e.g. 'carbonara', 'rendang', 'roast-chicken', 'confit', 'cheesecake', 'kung-pao', 'fried-chicken', 'brisket', 'wellington', 'cheese-souffle'). Use list_dishes() to see all available recipes and their aliases.
  • session_id · ? · optionnel
    Optional session ID to track an agent's improvement loop across multiple attempts.
  • master_json · ? · optionnel
    Optional user-supplied master SOP to verify against (BYO master, ADR-018), as a JSON string or object using the same schema as catalog masters (dish_name, steps[], required_ingredients[]; see get_master() for a live example). When provided, the bundled catalog is bypassed — the candidate is checked against YOUR spec — and dish_name may be omitted. The response pins the spec via master_hash (sha256) and master_source='user' so the verdict is replayable.
  • operator_id · ? · optionnel
    Optional audit identifier for the calling operator (letters, digits, hyphens; max 64 chars). Tags the verification in the tamper-evident log and compliance record. Defaults to 'anonymous'.
  • candidate_json · ? · optionnel
    The full candidate recipe as a JSON string or object. Expected schema: {"title": "<string>", "cuisine": "<string>", "serves": <int>, "ingredients": [{"name": "<string>", "quantity": "<string>"}], "steps": [{"step_number": <int>, "title": "<string>", "instruction_english": "<string>", "technique": "<string>", "estimated_temperature_c": <number or [min, max]>, "duration_minutes": <number or [min, max]>, "cooking_medium": "<string>"}]}
  • original_prompt · ? · optionnel
    RECOMMENDED for best results. Include the user's original cooking request. Copy the user's exact message that triggered this recipe (e.g., 'Make me a spicy vegan rendang' or 'Generate a traditional carbonara, but healthier'). WITHOUT this parameter: Guardian returns actionable findings with specific ingredient names and technique details — enough to fix most recipes. WITH this parameter: Guardian additionally activates safety context awareness (e.g., flagging honey for infants, raw egg for pregnant users) and personalised feedback matched to dietary needs and flavour preferences. Include it when the user's context matters for safety or personalisation.
  • response_format · string · optionnel
    Response format: 'json' (default — machine-actionable verdict, findings, and patches) or 'text' (human-readable report).

  Exemple d'appel

  {"name": "verify_recipe", "arguments": {"dish": "texte", "dish_name": "texte", "session_id": "texte", "master_json": "texte", "operator_id": "texte", "candidate_json": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.kaimeilabs.dev/mcp