RecipeBee
REMOTE · RECIPEBEE.APP
Discover, preview, and save recipes and meal plans with RecipeBee; private actions require OAuth.
Available components
Last scanned (1 day ago)
Scores higher than 55% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_recipe_content). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3778 tokens (~87/item across 43 items; 19 tools + 24 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 23 Oct 26 66
First indexed and scored.
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 23 Oct 2026 · Probed https://recipebee.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=recipebee.app | CN=YE2,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 60a61b245ba700caab6d93cdc336da70242 |
| SANs: recipebee.app, www.recipebee.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of recipebee.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| recipebee.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; base-uri 'none'; script-src 'unsafe-inline' https://recipebee.app; style-src 'unsafe-inline'; img-src data: https://recipebee.app https://api.recipebee.app https://cdn.recipebee.app https://images.recipebee.app; font-src 'none'; connect-src https://recipebee.app; form-action https://recipebee.app; frame-ancestors https://chatgpt.com https://claude.ai https://www.claude.ai |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recipebee.app/mcp | Verified | 200 | |
| http (plaintext) | http://recipebee.app/mcp | HTTPS enforced | 301 | https://recipebee.app/mcp |
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 →
attach_instruction_image Attach instructional photo ~204
Use after a structured recipe is saved and the user asks to attach its photos. Use the returned canonical stage/action ID and latest content revision. Supply a transferable host file descriptor or accessible HTTPS image URL, only with established reuse permission. Do not scrape private chats or claim access to search thumbnails. This saves no new recipe and uses no image-generation credits. Poll get_instruction_image for completion. If transfer is unavailable, offer RecipeBee upload. A failed photo never requires resaving the recipe.
| Name | Type | Req | Description |
|---|---|---|---|
| alt_text | string | – | – |
| caption | string | – | – |
| expected_revision | integer | yes | – |
| file | object | – | – |
| image_url | string | – | – |
| recipe_id | string | yes | – |
| reuse_permission | string | yes | Use only when the user owns the image or has established permission to save and use it. A search result or attribution alone does not establish permission. |
| target_id | string | yes | – |
| target_type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| operation | object | yes | – |
| persisted | boolean | yes | – |
No examples provided.
attach_recipe_image Attach MCP client image ~185
Use when the user wants to attach an image generated or uploaded in the current MCP client conversation to an existing private RecipeBee recipe. Prefer the Apps SDK file input when MCP client supplies file with download_url and file_id. Use image_url only for a URL selected or uploaded in the RecipeBee widget. If neither file nor image_url is available, return a pending selection and do not claim attachment. The widget picker is a fallback because native generated images may not be available in MCP client Files. Report attachment only after persisted=true and needs_image_selection=false. mode=replace changes which retained image is primary but does not delete the previous image; use it only after the user explicitly requests replacement. Do not use for a new RecipeBee-generated image.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | – | – |
| image_url | – | – | – |
| mode | string | – | – |
| recipe_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicate | boolean | yes | – |
| image | object | yes | – |
| is_public | boolean | yes | – |
| needs_image_selection | boolean | yes | – |
| persisted | boolean | yes | – |
| recipe | object | – | – |
| recipe_id | string | yes | – |
No examples provided.
commit_meal_plan_import Add meal plan to RecipeBee ~111
Use after prepare_meal_plan_import. Submit exactly one decision for every recipe. Use use_existing only with a recipe ID returned by preparation and only after the user chooses it; otherwise use create_new. This creates one private meal plan and its entries atomically, then renders the final RecipeBee card. Claim success only when persisted=true. The response may include an optional image batch link; never start image generation from MCP client.
| Name | Type | Req | Description |
|---|---|---|---|
| decisions | array | yes | – |
| draft_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicate | boolean | yes | – |
| entry_count | integer | yes | – |
| image_batch | – | – | – |
| meal_plan | object | yes | – |
| new_recipe_count | integer | yes | – |
| persisted | boolean | yes | – |
| recipes | array | yes | – |
| reused_recipe_count | integer | yes | – |
No examples provided.
generate_recipe_image Generate recipe image ~271
Request RecipeBee image generation for an existing private recipe. Generation may reserve existing RecipeBee image credits or consume a free-tier image allowance. On protocol 2026-07-28, the server requires an accepted confirmation form bound to this recipe and these image options; image_generation_confirmed is ignored. On older MCP clients, omit image_generation_confirmed until the user explicitly accepts, then set it to true on one retry. This tool never purchases credits or starts checkout; if the existing entitlement is unavailable, report the failure without directing the user to a purchase flow. Do not use for an image already generated or uploaded in this conversation. mode=add retains the current primary image. mode=replace changes which retained image is primary but does not delete the previous image; use it only after the user explicitly requests replacement.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | – | – |
| custom_prompt | – | – | – |
| image_generation_confirmed | boolean | – | For pre-2026 MCP clients only: set to true after explaining possible credit or free-allowance use and receiving the user’s explicit acceptance. Protocol 2026-07-28 ignores this value and collects con… |
| mode | string | – | – |
| recipe_id | string | yes | – |
| seed | – | – | – |
| style | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| image | object | yes | – |
| is_public | boolean | yes | – |
| persisted | boolean | yes | – |
| recipe | object | – | – |
| recipe_id | string | yes | – |
No examples provided.
get_image_generation_batch Get RecipeBee image batch status ~59
Read the progress of an optional RecipeBee image-generation batch returned by a meal-plan import. This tool never starts, charges, or cancels image generation; the user must confirm the batch in RecipeBee.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| access | object | yes | – |
| available_credits | integer | yes | – |
| completed_at | – | – | – |
| completed_count | integer | yes | – |
| confirmed_at | – | – | – |
| created_at | – | – | – |
| eligible_count | integer | yes | – |
| estimated_credits | integer | yes | – |
| estimated_selected_credits | integer | yes | – |
| failed_count | integer | yes | – |
| id | string | yes | – |
| image_credit_cost | integer | yes | – |
| items | array | yes | – |
| meal_plan_id | – | – | – |
| progress | object | yes | – |
| requested_count | integer | yes | – |
| requires_confirmation | boolean | yes | – |
| reserved_credits | integer | yes | – |
| skipped_count | integer | yes | – |
| source | string | yes | – |
| source_reference | – | – | – |
| status | string | yes | – |
| web_url | string | yes | – |
No examples provided.
get_instruction_image Get instructional photo status ~57
Read one attachment operation returned by attach_instruction_image. Never resave the recipe to retry a photo. Use show_recipe after completion to refresh the full recipe view.
| Name | Type | Req | Description |
|---|---|---|---|
| operation_id | string | yes | – |
| recipe_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| operation | object | yes | – |
| persisted | boolean | yes | – |
No examples provided.
get_recipe_image Check recipe image ~35
Check the private AI image status for an existing RecipeBee recipe after image generation was requested.
| Name | Type | Req | Description |
|---|---|---|---|
| recipe_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| image | object | yes | – |
| is_public | boolean | yes | – |
| persisted | boolean | yes | – |
| recipe | object | – | – |
| recipe_id | string | yes | – |
No examples provided.
list_saved_meal_plans List private RecipeBee meal plans ~77
Browse or search the connected user's private RecipeBee meal plans. Use only when the user asks to browse or search meal plans. Returns paginated summaries; use show_meal_plan only for a plan the user selects.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| per_page | integer | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| has_more | boolean | yes | – |
| items | array | yes | – |
| next_cursor | – | yes | – |
| per_page | integer | yes | – |
| prev_cursor | – | yes | – |
No examples provided.
list_saved_recipes List private RecipeBee recipes ~75
Browse or search the connected user's private RecipeBee recipe library. Use only when the user asks to browse or search saved recipes. Returns a small paginated summary; use show_recipe only for a recipe the user selects.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| per_page | integer | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| has_more | boolean | yes | – |
| items | array | yes | – |
| next_cursor | – | yes | – |
| per_page | integer | yes | – |
| prev_cursor | – | yes | – |
No examples provided.
open_recipebee_kitchen Open RecipeBee Kitchen ~38
Open the connected user's private recipe and meal-plan library in the ChatGPT sidebar. The app reads only the library section the user opens.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| opened | boolean | yes | – |
No examples provided.
prepare_meal_plan_import Prepare meal-plan import ~125
Use only after the user explicitly asks to add a completed meal plan to RecipeBee. This stateful, data-only step checks private recipes for exact or possible matches and creates a short-lived import draft without creating recipes or a meal plan or rendering a RecipeBee card. Do not use for chat-only meal planning. Wait for explicit recipe choices when matches are returned.
| Name | Type | Req | Description |
|---|---|---|---|
| assignments | array | yes | – |
| description | – | – | – |
| end_date | string | yes | – |
| recipes | array | yes | – |
| start_date | string | yes | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assignment_count | integer | yes | – |
| draft_id | string | yes | – |
| expires_at | – | – | – |
| meal_plan_id | – | – | – |
| plan | object | yes | – |
| recipes | array | yes | – |
| requires_choices | boolean | yes | – |
| status | string | yes | – |
| unique_recipe_count | integer | yes | – |
No examples provided.
preview_meal_plan Preview meal plan ~91
Use when the user asks to review a meal plan without adding it to RecipeBee. This chat-only, data-only tool never writes recipes or meal plans and does not render a RecipeBee card.
| Name | Type | Req | Description |
|---|---|---|---|
| assignments | array | yes | – |
| description | – | – | – |
| end_date | string | yes | – |
| recipes | array | yes | – |
| start_date | string | yes | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| is_public | boolean | yes | – |
| persisted | boolean | yes | – |
| plan | object | yes | – |
No examples provided.
preview_recipe Preview recipe ~247
Use when the user asks to preview or review a complete recipe without saving it. Include realistic integer prep_time_minutes, cook_time_minutes, and total_time_minutes values in every complete recipe. Estimate them when the user does not specify times; use 0 only when that part genuinely takes no time. For recipes with components or cooking stages, provide content sections and omit flat ingredients and steps. Validate and render the recipe without persistence. Do not call as an intermediate step when the user has already explicitly asked to save.
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | – | For multi-component recipes, provide ingredient and instruction sections here and omit flat ingredients and steps. |
| cook_time_minutes | integer | yes | Estimated cooking time in minutes. Use 0 only when no cooking is needed. |
| ingredients | array | – | – |
| notes | – | – | – |
| prep_time_minutes | integer | yes | Estimated preparation time in minutes. Use 0 only when no preparation is needed. |
| servings | – | – | – |
| steps | array | – | – |
| summary | – | – | – |
| tags | – | – | – |
| title | string | yes | – |
| total_time_minutes | integer | yes | Total elapsed time in minutes. Keep this consistent with the preparation and cooking steps. |
| Name | Type | Req | Description |
|---|---|---|---|
| is_public | boolean | yes | – |
| persisted | boolean | yes | – |
| recipe | object | yes | – |
No examples provided.
remove_instruction_image Remove instructional photo ~82
Use only after the user asks to remove a specific stage or action photo. Read the latest recipe first and supply its content revision plus the photo operation ID. Removal is permanent for this photo; it does not change recipe text or require another photo.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_revision | integer | yes | – |
| operation_id | string | yes | – |
| recipe_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| operation | object | yes | – |
| persisted | boolean | yes | – |
No examples provided.
save_recipe Save private recipe ~318
Use when the user explicitly asks to save a complete recipe privately. Include realistic integer prep_time_minutes, cook_time_minutes, and total_time_minutes values in every complete recipe. Estimate them when the user does not specify times; use 0 only when that part genuinely takes no time. Use content sections for recipes with components or cooking stages; omit flat ingredients and steps when content is present. Save exactly once. If the user asks for RecipeBee image generation, disclose that it may reserve existing image credits or consume a free-tier image allowance and wait for explicit acceptance before using save_recipe_with_image. If the user wants to attach an MCP client-generated or uploaded stage/action photo, save the recipe first, then use attach_instruction_image with the returned target ID and latest content revision. Use attach_recipe_image only for a hero/gallery photo. Do not publish or use browser control.
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | – | For multi-component recipes, provide ingredient and instruction sections here and omit flat ingredients and steps. |
| cook_time_minutes | integer | yes | Estimated cooking time in minutes. Use 0 only when no cooking is needed. |
| ingredients | array | – | – |
| notes | – | – | – |
| prep_time_minutes | integer | yes | Estimated preparation time in minutes. Use 0 only when no preparation is needed. |
| servings | – | – | – |
| steps | array | – | – |
| summary | – | – | – |
| tags | – | – | – |
| title | string | yes | – |
| total_time_minutes | integer | yes | Total elapsed time in minutes. Keep this consistent with the preparation and cooking steps. |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicate | boolean | yes | – |
| is_public | boolean | yes | – |
| persisted | boolean | yes | – |
| recipe | object | yes | – |
No examples provided.
save_recipe_with_image Save recipe with image ~418
Save a complete recipe privately and request RecipeBee image generation. Image generation may reserve existing RecipeBee image credits or consume a free-tier image allowance. On protocol 2026-07-28, the server requires an accepted confirmation form bound to these exact recipe and image options; image_generation_confirmed is ignored. On older MCP clients, omit image_generation_confirmed until the user explicitly accepts, then set it to true on one retry. No recipe is saved before confirmation. Once confirmed, save privately and queue the moderated image pipeline once; the recipe remains saved if image generation fails or is unavailable. This tool never purchases credits or starts checkout. For an MCP client-generated or uploaded image, use save_recipe followed by attach_recipe_image instead. Do not call preview_recipe or save_recipe first. Include realistic integer prep_time_minutes, cook_time_minutes, and total_time_minutes values in every complete recipe. Estimate them when the user does not specify times; use 0 only when that part genuinely takes no time.
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | – | For multi-component recipes, provide ingredient and instruction sections here and omit flat ingredients and steps. |
| cook_time_minutes | integer | yes | Estimated cooking time in minutes. Use 0 only when no cooking is needed. |
| image | object | – | – |
| image_generation_confirmed | boolean | – | For pre-2026 MCP clients only: set to true after explaining possible credit or free-allowance use and receiving the user’s explicit acceptance. Protocol 2026-07-28 ignores this value and collects con… |
| ingredients | array | – | – |
| notes | – | – | – |
| prep_time_minutes | integer | yes | Estimated preparation time in minutes. Use 0 only when no preparation is needed. |
| servings | – | – | – |
| steps | array | – | – |
| summary | – | – | – |
| tags | – | – | – |
| title | string | yes | – |
| total_time_minutes | integer | yes | Total elapsed time in minutes. Keep this consistent with the preparation and cooking steps. |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicate | boolean | yes | – |
| image | object | yes | – |
| is_public | boolean | yes | – |
| persisted | boolean | yes | – |
| recipe | object | yes | – |
No examples provided.
show_meal_plan Show private RecipeBee meal plan ~53
Read the selected private meal plan and its scheduled recipes. Use only after the user selects or names a plan. This tool is read-only and does not edit the plan.
| Name | Type | Req | Description |
|---|---|---|---|
| meal_plan_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meal_plan | object | yes | – |
No examples provided.
show_recipe Show RecipeBee recipe ~91
Use after attach_recipe_image or generate_recipe_image to render the current authoritative private recipe and image status, or when the user explicitly asks to view an existing recipe. Do not call immediately after save_recipe or save_recipe_with_image because those tools already return the authoritative saved recipe. Call it once after a later image mutation; do not use it repeatedly or as a substitute for saving.
| Name | Type | Req | Description |
|---|---|---|---|
| recipe_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| image | object | yes | – |
| is_public | boolean | yes | – |
| persisted | boolean | yes | – |
| recipe | object | – | – |
| recipe_id | string | yes | – |
No examples provided.
update_recipe_content Update recipe sections ~129
Use only after reading the saved recipe with show_recipe and receiving a direct request to change its ingredients or instructions. Send the full content document and its current revision. Preserve existing section and item IDs for unchanged content; omitted sections or actions are deleted. New sections and actions can omit IDs. This replaces grouped text atomically and advances the revision. Photos remain optional and are not changed by this tool. On a revision conflict, read the recipe again and reconcile the requested edit before retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | yes | – |
| expected_revision | integer | yes | – |
| recipe_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | yes | – |
| persisted | boolean | yes | – |
No examples provided.
How do I install the RecipeBee MCP server?
RecipeBee is a hosted endpoint at https://recipebee.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · recipebee.app
claude mcp add --transport http praisondani-recipebee 'https://recipebee.app/mcp'
What is the RecipeBee MCP server?
RecipeBee is an MCP server listed in the public MCP registry as io.github.praisondani/recipebee. Discover, preview, and save recipes and meal plans with RecipeBee; private actions require OAuth. This page covers its hosted endpoint (https://recipebee.app/mcp).
Is the RecipeBee MCP server safe to use?
RecipeBee scores 66 out of 100 on VerifyMCP. 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 RecipeBee MCP server expose?
RecipeBee exposes 19 tools: preview_meal_plan, prepare_meal_plan_import, commit_meal_plan_import, get_image_generation_batch, list_saved_recipes, and 14 more. Their descriptions and schemas cost roughly 2,666 tokens of context every time the server is loaded.
Does the RecipeBee MCP server require authentication?
No. We connected to RecipeBee without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RecipeBee MCP server still maintained?
RecipeBee is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.