Home / MCP registry index / io.github.praisondani/recipebee
RecipeBee
io.github.praisondani/recipebee in the official MCP registry.
Endpoint https://recipebee.app/mcp. Source: github.com/praisondani/recipebee-cursor-plugin.
The registry describes it as: Discover, preview, and save recipes and meal plans with RecipeBee; private actions require OAuth.
We read its 19 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
preview_meal_plan prepare_meal_plan_import commit_meal_plan_import get_image_generation_batch list_saved_recipes list_saved_meal_plans show_meal_plan open_recipebee_kitchen preview_recipe attach_instruction_image update_recipe_content get_instruction_image remove_instruction_image save_recipe save_recipe_with_image show_recipe attach_recipe_image generate_recipe_image get_recipe_image
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-praisondani-recipebee)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.