com.recipes-daily/recipes

Est-ce que com.recipes-daily/recipes est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.recipes-daily/recipes » 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 4 outils

• find_recipes_by_ingredients≈ 280 tokens

  Given ingredients someone has, rank the recipes at recipes-daily.com by how many of them each one uses and name what is missing from the rest. Matches by ingredient text, not identity — a near-miss on the name still counts, but two ingredients that are genuinely different words for the same thing (courgette/zucchini) may not. This is not a substitution finder: if nothing uses every ingredient given, the closest partial matches are still worth reading — deciding whether a missing ingredient can be swapped or skipped is the caller's call, not this tool's.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Recipes to return, ranked by coverage.
  • ingredients · array · optionnel
    What is on hand, one ingredient per entry — e.g. ["broccoli", "chicken breast", "lemon"].

  Exemple d'appel

  {"name": "find_recipes_by_ingredients", "arguments": {"limit": 1, "ingredients": []}}

  Exemple de retour

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

• read_guide≈ 232 tokens

  Read the full text of a cooking guide from recipes-daily.com, as markdown. Call this when search_recipes lists a guide that answers the question — how or why something works in the kitchen, how to store or substitute an ingredient, how to use a piece of equipment — and answer from what it says rather than from memory, citing its URL. Pass the guide URL exactly as search_recipes returned it. For recipes, use show_recipes instead: a recipe is a page the person cooks from, not text to retell.

  Paramètres, retour & exemple (1)

  Paramètres

  • guide · string · optionnel
    The guide to read, as the absolute recipes-daily.com URL search_recipes returned — e.g. "https://recipes-daily.com/guides/preparations/why-do-dried-beans-take-so-long-to-cook".

  Exemple d'appel

  {"name": "read_guide", "arguments": {"guide": "texte"}}

  Exemple de retour

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

• search_recipes≈ 393 tokens

  Find something to cook, from the recipes published at recipes-daily.com. Call this for any question about what to make — a dish by name, a cuisine, a weeknight time budget, a week of dinners — rather than answering from memory, because each result is a real page with quantities, timings and a photograph behind it. For what to cook from ingredients someone already has, call find_recipes_by_ingredients instead: this tool requires every query word to appear in one recipe, so several ingredient names in one search return nothing rather than a coverage report. Returns a shortlist — title, absolute URL, description, total time, servings and categories — so candidates can be ruled out without opening them. The first page also lists matching cooking guides, for how and why questions about technique, storage and substitutions; read one in full with read_guide.

  Paramètres, retour & exemple (3)

  Paramètres

  • page · integer · optionnel
    1-based. The response names the next page when there is one.
  • limit · integer · optionnel
    Results per page.
  • query · string · optionnel
    What to search for. Recipes are matched on titles and descriptions, so a word or short phrase matches better than a full question, and there are no boolean operators. Omit it to list every recipe, newest first.

  Exemple d'appel

  {"name": "search_recipes", "arguments": {"page": 1, "limit": 1, "query": "texte"}}

  Exemple de retour

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

• show_recipes≈ 220 tokens

  Draw recipes as picture cards the person can click through to. Takes any recipes-daily.com recipe URLs you are already holding. Whenever you name recipes from this server in an answer, pass those same ones here — the cards are how a person actually gets to a recipe, and they appear only if you call this. Order is kept, so put the strongest recommendation first.

  Paramètres, retour & exemple (1)

  Paramètres

  • recipes · array · optionnel
    The recipes to draw, as absolute recipes-daily.com URLs — e.g. ["https://recipes-daily.com/make/chicken-piccata-pan-fried-25-minute"]. A bare slug works too. Order is kept, so put the strongest recommendation first.

  Exemple d'appel

  {"name": "show_recipes", "arguments": {"recipes": []}}

  Exemple de retour

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

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://recipes-daily.com/mcp