Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cookidoo MCP

PYPI · COOKIDOO-MCP · SCANNED SEP 20

Create, translate, and plan Cookidoo recipes with guided Thermomix actions and shopping lists.

Available components

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2108 tokens (~131/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 68% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_recipe_from_meal_plan" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Cookidoo MCP server?

Cookidoo MCP runs locally as a PyPI package, launched with uvx cookidoo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · cookidoo-mcp

# add to Claude Code
claude mcp add vitaliemiron-cookidoo-mcp -- uvx cookidoo-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "vitaliemiron-cookidoo-mcp": {
      "command": "uvx",
      "args": [
        "cookidoo-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vitaliemiron-cookidoo-mcp": {
      "command": "uvx",
      "args": [
        "cookidoo-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add vitaliemiron-cookidoo-mcp -- uvx cookidoo-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vitaliemiron-cookidoo-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "cookidoo-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vitaliemiron-cookidoo-mcp --command uvx --arg cookidoo-mcp
# ~/.hermes/config.yaml
mcp_servers:
  vitaliemiron-cookidoo-mcp:
    command: "uvx"
    args: ["cookidoo-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vitaliemiron-cookidoo-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "cookidoo-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add vitaliemiron-cookidoo-mcp -t stdio -c uvx -a cookidoo-mcp
// mcp.json
{
  "mcpServers": {
    "vitaliemiron-cookidoo-mcp": {
      "command": "uvx",
      "args": [
        "cookidoo-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 −2
    • Stability: pass → 0.80 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/cookidoo-mcp@1.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~1,844 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_recipes_to_meal_plan ~139

Add one or more recipes to a Cookidoo meal-plan day. Mixed official IDs (for example r460132) and custom recipe ULIDs are supported when recipe_source is auto. Separate IDs with commas, spaces, or newlines. The updated day is returned after Cookidoo confirms the change.

NameTypeReqDescription
datestringyesTarget day in YYYY-MM-DD format.
dry_runbooleanValidate and preview the exact calendar change without sending it to Cookidoo.
recipe_idsstringyesOne or more Cookidoo recipe IDs.
recipe_sourcestringauto, official, or custom.
NameTypeReqDescription
resultstringyes

No examples provided.

calculate_annotation_position ~90

Calculate Cookidoo's offset and length for text inside a recipe step. Cookidoo uses JavaScript UTF-16 character positions, which differ from normal Python string indexes when text before the marker contains emoji. Use this tool for every TTS, MODE, INGREDIENT, and VOLUME annotation.

NameTypeReqDescription
markerstringyes
occurrenceinteger
textstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

connect_to_cookidoo ~130

Authenticate with Cookidoo and store the session. This tool must be called before using other Cookidoo tools. It will: 1. Load your Cookidoo credentials from the .env file 2. Normalize and validate the optional COOKIDOO_COUNTRY and COOKIDOO_LANGUAGE values (default ro/en) 3. Authenticate with the matching Cookidoo platform localization 4. Store the authenticated session for use by other tools Returns: str: Success message confirming connection Raises: ValueError: If credentials are missing from .env file Exception: If authentication fails

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

copy_recipe_to_custom ~89

Copy an official Cookidoo recipe into the account's custom recipes. This is the supported way to obtain the full ingredients and instructions of an official recipe before translating or editing it. Set dry_run to true to validate and preview creation of the private copy without changing the account.

NameTypeReqDescription
dry_runboolean
recipe_idstringyes
servingsinteger
NameTypeReqDescription
resultstringyes

No examples provided.

generate_recipe_structure ~212

Generate and validate a recipe structure ready for upload to Cookidoo. This tool helps you structure your recipe data properly before uploading. It validates all fields and returns a JSON structure that can be used with the upload_custom_recipe tool. Always put weighing/adding ingredients in one step and the subsequent chopping, mixing, cooking, or kneading action in a separate step.

NameTypeReqDescription
hintsstringOptional cooking tips, one per line or comma-separated
ingredientsstringyesIngredients list, one per line or comma-separated
namestringyesRecipe name (required)
prep_timeintegerPreparation time in minutes (default: 30)
servingsintegerNumber of servings (default: 4, range: 1-20)
stepsstringyesCooking steps, one per line or numbered. Ingredient additions and machine actions must be on separate lines.
total_timeintegerTotal cooking time in minutes (default: 60)
NameTypeReqDescription
resultstringyes

No examples provided.

get_custom_recipe_details ~66

Get the full text content of a recipe in the account's custom recipes. Unlike get_recipe_details, this endpoint includes preparation instructions. It returns plain ingredient and instruction text; use the update tools to add or replace guided-cooking annotations.

NameTypeReqDescription
recipe_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_meal_plan_week ~104

Get Cookidoo's complete seven-day meal-plan window. Cookidoo normally omits empty days and returns custom recipes as bare IDs. This tool fills all seven days starting with the requested date and resolves custom recipe IDs to names, images, durations, and links. This matches the `?date=YYYY-MM-DD` parameter used by Cookidoo's web planner.

NameTypeReqDescription
datestringyesFirst day of the seven-day window, formatted YYYY-MM-DD.
NameTypeReqDescription
resultstringyes

No examples provided.

get_recipe_details ~78

Get detailed information about a specific recipe by its ID. Use this tool to get full details about a recipe for inspiration before creating your own custom recipe. You must be connected first using connect_to_cookidoo.

NameTypeReqDescription
recipe_idstringyesThe Cookidoo recipe ID (e.g., "r59322", "r907015")
NameTypeReqDescription
resultstringyes

No examples provided.

get_shopping_list_ingredients ~88

Get Cookidoo shopping-list ingredients grouped by recipe.

NameTypeReqDescription
include_additional_itemsbooleanInclude manually added shopping-list items.
include_ownedbooleanInclude ingredients already marked as owned. Defaults to false so grocery workflows receive only products still needed.
recipe_idOptional exact recipe ID from the shopping list. Omit it to return every recipe.
NameTypeReqDescription
resultstringyes

No examples provided.

move_recipe_in_meal_plan ~133

Move one recipe from one Cookidoo calendar day to another. The recipe is added to the target first and then removed from the source. If removal fails, a newly-added target entry is rolled back.

NameTypeReqDescription
dry_runbooleanValidate and preview both calendar operations without sending either one to Cookidoo.
from_datestringyesExisting day in YYYY-MM-DD format.
recipe_idstringyesOfficial or custom Cookidoo recipe ID.
recipe_sourcestringauto, official, or custom.
to_datestringyesNew day in YYYY-MM-DD format.
NameTypeReqDescription
resultstringyes

No examples provided.

remove_recipe_from_meal_plan ~86

Remove one recipe from a Cookidoo meal-plan day.

NameTypeReqDescription
datestringyesCalendar day in YYYY-MM-DD format.
dry_runbooleanValidate and preview the removal without sending it to Cookidoo.
recipe_idstringyesOfficial or custom Cookidoo recipe ID.
recipe_sourcestringauto, official, or custom.
NameTypeReqDescription
resultstringyes

No examples provided.

update_custom_recipe_ingredients ~102

Replace a custom recipe's ingredients. ingredients_json must be a JSON array. Each item may be plain ingredient text or an INGREDIENT object containing a VOLUME annotation. This partial update preserves the recipe's other fields. Set dry_run to true to validate and return the full replacement ingredient list without patching Cookidoo.

NameTypeReqDescription
dry_runboolean
ingredients_jsonstringyes
recipe_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

update_custom_recipe_steps ~147

Replace a custom recipe's preparation steps. steps_json must be a JSON array. Each item may be plain step text or a STEP object containing TTS, MODE, and/or INGREDIENT annotations. This partial update preserves the recipe's other fields. Always use separate steps for weighing/adding ingredients and for the following cooking, mixing, chopping, or kneading action. A single step cannot contain both INGREDIENT and TTS/MODE annotations. Set dry_run to true to validate and return the full replacement step list without patching Cookidoo.

NameTypeReqDescription
dry_runboolean
recipe_idstringyes
steps_jsonstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

upload_custom_recipe ~95

Upload a custom recipe to your Cookidoo account. This tool creates a brand new recipe from scratch on your Cookidoo account. Use 'generate_recipe_structure' first to validate your recipe data, then pass the resulting JSON to this tool.

NameTypeReqDescription
dry_runbooleanValidate and preview the complete new recipe without creating it in Cookidoo.
recipe_jsonstringyesThe validated recipe JSON from generate_recipe_structure
NameTypeReqDescription
resultstringyes

No examples provided.

upload_custom_recipe_image ~130

Upload a local image and attach it to a custom Cookidoo recipe. The file is converted to JPEG when necessary (including WebP), uploaded through Cookidoo's signed customer-recipe image flow, and attached with isImageOwnedByUser enabled. Cookidoo accepts images up to 10 MB.

NameTypeReqDescription
dry_runbooleanRead and validate the local image, then preview the upload and recipe attachment without sending either request.
image_pathstringyesAbsolute or user-relative path to a local image file.
recipe_idstringyesThe custom Cookidoo recipe ID.
NameTypeReqDescription
resultstringyes

No examples provided.

validate_guided_recipe_structure ~155

Validate a complete custom recipe, including guided-cooking annotations. Step annotations use Cookidoo's exact request schema: - TTS: manual time, temperature, speed, and direction - MODE: Dough, Blend, Turbo, Warm Up, Rice Cooker, Steaming, or Browning - INGREDIENT: a linked ingredient for on-device weighing INGREDIENT annotations must be in ingredient-only steps. TTS and MODE annotations belong in following, separate machine-action steps. Every annotation position is a zero-based JavaScript UTF-16 range into its enclosing step text. VOLUME positions use their enclosing ingredient text. Use calculate_annotation_position instead of normal Python string indexes.

NameTypeReqDescription
recipe_jsonstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the Cookidoo MCP server?

Cookidoo MCP is listed in the public MCP registry as io.github.vitaliemiron/cookidoo-mcp. Create, translate, and plan Cookidoo recipes with guided Thermomix actions and shopping lists. This page covers its PyPI package (cookidoo-mcp).

Is the Cookidoo MCP server safe to use?

Cookidoo MCP scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Cookidoo MCP server expose?

Cookidoo MCP exposes 16 tools: connect_to_cookidoo, get_recipe_details, get_custom_recipe_details, get_shopping_list_ingredients, get_meal_plan_week, and 11 more. Their descriptions and schemas cost roughly 1,844 tokens of context every time the server is loaded.

Is the Cookidoo MCP server still maintained?

Cookidoo MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.