# Befana Recipes

> Ad-free recipes with amounts in every step: search, scale, plan meals, build shopping lists.

- name: app.befana/befana
- version: 0.2.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 81/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/app.befana%2Fbefana
- tools: https://api.protogrid.dev/v1/servers/app.befana%2Fbefana/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "befana": {
      "type": "http",
      "url": "https://befana.app/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-6d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 81/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 24 of 24 tools declare readOnlyHint or destructiveHint
- warn `tools.directory_hints`: 17 of 24 tools declare all four hints; missing: search_recipes (destructiveHint, idempotentHint); get_recipe (destructiveHint, idempotentHint); plan_meals (idempotentHint); …
- warn `tools.token_cost`: about 13,897 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 3 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 24, about 13,897 tokens to load them all
- tool set hash: eee354e2aca7fde7f7c8f8deaf5da3a5
- tools last changed: 2026-10-20T15:05:47.479Z
- badge: [![protogrid quality](https://protogrid.dev/badge/app.befana/befana.svg)](https://protogrid.dev/servers/app.befana/befana)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-20 `update_recipe` changed (inputSchema, outputSchema)
- 2026-10-20 `get_recipe` changed (outputSchema)
- 2026-10-20 `search_recipes` changed (inputSchema)
- 2026-10-20 `get_my_stats` added
  - How the cook's own recipes are doing: views, shares, prints, cooks, saves, versions and ratings, in total and by day, per recipe and by region. Use when a cook who publishes asks "how's my recipe doing?", "how many people cooked my dal?", "what's my most popular recipe?". Counts only, never who: the cook's own activity is left out, and a cook is someone who finished the last step, said they made it, or printed it. Lead with line, then the top recipe with its url; quote definitions.cook if asked what counts. Same numbers as /me/stats on the website.
- 2026-10-20 `update_recipe` changed (inputSchema, outputSchema)
- 2026-10-20 `update_meal_plan` changed (outputSchema)
- 2026-10-20 `plan_meals` changed (outputSchema)
- 2026-10-20 `update_shopping_list` changed (description, inputSchema, outputSchema)
  - before: Change a saved list after the cook answers what build_shopping_list or plan_meals set aside as likely_have. remove: things they have (they come off, and count as left off); need: set-aside things they're out of (they move to the buy aisles); add: anything else for the trip, as they said it. Use when the cook says "I have the flour and oil" or "I'm out of chili flakes". Changes only this list, never the pantry: ask "Want me to remember these for next time?" first, then call pantry. Returns the pared list, its estimate and the order offer.
  - after: Change a saved list after the cook answers what build_shopping_list or plan_meals set aside as likely_have, or says how the trip went. remove: things they have (they come off, and count as left off); need: set-aside things they're out of (they move to the buy aisles); add: anything else for the trip, as they said it; outcomes: what happened at the store per item (bought, skipped, bought_elsewhere with the store they name). Use when the cook says "I have the flour and oil", "I'm out of chili flakes" or "skipped the salmon, got the bread at the bakery". Changes only this list, never the pantry: ask "Want me to remember these for next time?" first, then call pantry. Returns the pared list, its estimate and the order offer.
- 2026-10-20 `build_shopping_list` changed (outputSchema)
- 2026-10-20 `get_recipe` changed (outputSchema)

Full history: https://api.protogrid.dev/v1/servers/app.befana%2Fbefana/changes

## Remotes

- https://befana.app/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (24)

- `build_shopping_list`: Merge recipes (each at its own servings) and anything else into one shopping list by aisle, in what a store sells (10 cloves garlic → 1 head). Use for "make me a list", "what do I need to buy?" or "add paper towels and 2 lb bananas" (extra_items keep the cook's amounts). What the cook has stays off (left_off); staples and small amounts of bulk items (3 tbsp flour) come back as likely_have, not bought: ask which they have or are out of, then update_shopping_list. Items that hit their allergies are flagged. Signed in, the list is saved and returns a shareable url and an id for order_groceries; signed out it comes back unsaved (keep: true asks them to sign in).
- `cook_profile`: Read a cook's public Befana page, or change the signed-in cook's own. Use when the cook asks "who wrote this?", "show me more from this cook", "what's on my profile?", or wants their name, about me, links or handle changed. Pass handle (any recipe's author.handle) to read that page; nothing to read their own (signed in). To change their own, pass update with only the fields to change, after telling them exactly what will change and getting a yes (cook_confirmed). Never write about-me text for them. Returns name, about, links and public recipes with urls; ai_chef true means an AI chef persona. Nothing private is ever on a profile.
- `create_recipe`: Publish a recipe to Befana. Use with draft_id from draft_recipe once the cook has seen and confirmed the draft, passing only the fields they changed; never publish pasted text straight from fields. Pass fields without a draft only for a recipe you worked out with the cook in this conversation, after showing it to them. Steps use ingredient tags, never typed amounts: "Whisk {flour} with {salt}". Recipes are public and appear under My recipes unless visibility is "private" (just for the cook); an exact copy of one the cook already has is refused (use update_recipe). tested marks it cooked and timed only when the cook says they made it; ask, never assume. Returns the url and any warnings.
- `delete_recipe`: Delete a recipe the cook owns, for good, when nobody else has touched it (no versions, reviews or saves by other cooks). Use when the cook says "delete that test recipe", "get rid of it". Without confirm it only reports what would go and whether it can; name the recipe, get a yes, then call with confirm: true. A recipe others have cooked or saved can't be deleted: the answer points at update_recipe({ unpublished: true }), which takes it off Befana for everyone but the cook and can be undone.
- `draft_recipe`: Turn a recipe the cook pasted, typed or linked into a draft to check: ingredients matched, steps in plain words with the amounts as tags, servings, times and timers filled in. Nothing is published. Use when the cook says "save my grandma's meatballs", "add this one" with a link, or shows you a recipe card (read it yourself and pass the text). Show the draft, point out the guessed fields, then publish with create_recipe({ draft_id }) once they confirm. existing means it's already on Befana: send them there (save_recipe, fork_recipe), and add_anyway only if they say it's a different recipe. blocked means the site only opens for its readers: pass the page's text with source_url if you can see it.
- `fork_recipe`: Save the cook's own version of someone else's recipe, linked to the original, which never changes. Use when the cook says "make it dairy-free and keep that", "halve the sugar", "save it for 8". Pass only what changes; ingredients or steps, if passed, are the complete new list (get_recipe first and edit it). Before calling, show the cook the changed ingredients and steps and get a yes; never save silently. It's named after the change unless you pass title. Public by default; visibility "private" keeps it just for the cook. The same change again returns their existing version (already_existed). On the cook's own recipe use update_recipe; this refuses.
- `generate_placeholder_cover`: Draw a labeled illustration of the dish for a recipe the cook owns that has no photo, so it looks finished until they add a real one. Use when the cook says "it needs a picture" or accepts the offer after create_recipe. Ask first; it takes up to a minute. It's drawn from the recipe's own text, labeled "Illustration, not a photo of this dish" everywhere, never counted as a photo, and never replaces a cook's photo (that's a refusal, not an error). When image generation is off, say so and point to the photo upload on the website.
- `get_cook_steps`: A recipe as hands-free steps for cooking along: a gather list, then one step at a time with its amounts, the ingredients it uses, its tip and any timer. Use when the cook says "walk me through it", "I'm cooking it now", "what's next?" (pass step for just that one, or from_step to pick up where they left off). Give one step per reply and offer the step's timer. The recipe url shows the same steps as a checklist on their phone. Works signed out.
- `get_my_kitchen`: What the cook keeps on Befana: saved recipes, recipes they published, their own versions, shopping lists and meal plans, their ratings, a pantry count. Use when the cook asks "what did I save?", "pull up last week's list", "show my recipes", or (section: photos) "which of my recipes need a better photo?". Same as My Kitchen on the website. If newly_assigned is present, say its line first, once (Befana added those recipes; hand_back_recipe returns one that isn't theirs). If fixes_asked is present, pass the fixes on once and offer to make them with update_recipe after showing the changes.
- `get_my_stats`: How the cook's own recipes are doing: views, shares, prints, cooks, saves, versions and ratings, in total and by day, per recipe and by region. Use when a cook who publishes asks "how's my recipe doing?", "how many people cooked my dal?", "what's my most popular recipe?". Counts only, never who: the cook's own activity is left out, and a cook is someone who finished the last step, said they made it, or printed it. Lead with line, then the top recipe with its url; quote definitions.cook if asked what counts. Same numbers as /me/stats on the website.
- `get_recipe`: One recipe in full, scaled to any servings, US or metric, with every amount written into the step that uses it, so steps can be read aloud as they are. Use when the cook picks a recipe, asks "how much butter is that in tablespoons?" (pass units_for; the list and the steps follow, don't convert yourself), or wants a change ("make it dairy-free": substitute returns swaps that respect their allergies and diet; show the changed ingredients and steps, then save on their yes with fork_recipe, or update_recipe on their own). Returns the recipe, its url, step tips to pass on, and your_versions when the cook already has their own version (offer it). Mention chef_note only if asked. Works signed out.
- `hand_back_recipe`: Hand back a recipe the Befana team added to the cook's kitchen (get_my_kitchen newly_assigned) when the cook says "that one isn't mine". Keeping it is the default and needs nothing. Confirm with the cook first; it works once per recipe.
- `order_groceries`: Send a shopping list to a grocer near the cook: into their cart where the store allows it (King Soopers and other Kroger stores, once connected), else one list link, else a search link per item. Use when the cook says "order these", "get it delivered", "send it to my store". No saved store: it asks their ZIP, then lists nearby grocers (choose_store); call again with store and zip, which saves it. A cart grocer first returns cart_preview: tell the cook its say (flagged items and total only), apply their changes as edits, then call with preview_id and confirm: true. Share share_url with the cook (the order is theirs: Befana's order page uses their saved store and sign-in); list_url is the link for the household. Befana never picks a brand. Keep commission_disclosure in parentheses right after the link, once.
- `pantry`: Read or change the cook's pantry: food on hand and staples, which Befana leaves off shopping lists and uses for what-can-I-make. Use when the cook says what they have or ran out of ("I've got chicken thighs and half an onion", "we're out of eggs"), corrects it, or asks what's in it. Pass their words verbatim as text; or add/remove names; a fridge photo goes in photo (an upload name). No arguments reads it. Saying what they have is the cook's yes: save it and read the change back in one line. Never add what the cook didn't say. Returns the change (unsure lists what didn't read as food) or the whole pantry.
- `plan_meals`: Plan dinners for the coming days and return the finished week in one call: the plan by day (varied bases and methods, perishables first, one meal new to the cook with why), the merged shopping list (list), prep_order, substitutions and one true line (say). Use when the cook says "what should we eat this week?", "plan dinners", "groceries for the week", "four dinners under $80" (max_budget), or has people over (occasion, guest_notes). Their preferences and pantry apply. Show the plan with say, ask the one question in next_steps, then the list; nothing is ordered. A swap goes to update_meal_plan with plan_id. Signed out it comes back unsaved (keep: true asks to sign in).
- `preferences`: Read or change the cook's Befana preferences: allergies, diet, avoid list, household size, units, weeknight time, skill, equipment, cuisines, store, privacy, and how they want you to work, all applied to every tool. No arguments reads them. For a change the cook asks for in their own words ("switch me to metric", "set us to 4 people"), save with cook_confirmed. Allergies, diets, the avoid list, privacy, a change you suggest or a passing mention ("usually it's 4 of us") need a yes first: pass the change without cook_confirmed (nothing is saved), ask the cook confirm.say, then call again with cook_confirmed. Never infer an allergy or diet. Lists replace the saved list.
- `rate_recipe`: Post the cook's star rating (1 to 5) and comment, and mark that they made it. Use when the cook says "that was great, five stars" or "I made the chili, a bit too salty". One rating per cook per recipe: calling again updates it, and a comment left out is kept. Refuses the cook's own recipe. Post only what the cook said; ask for the stars if they didn't give any. With made_it it finishes their cook and may offer to take what the recipe used off the pantry.
- `report_content`: Flag a recipe, review, photo or a cook's profile for Befana's moderators: spam, offensive, unsafe as written, copied without permission, not a recipe, or something else. Use only when the cook asks ("report this review", "this recipe is dangerous"), in their words. Moderators review every report; nothing is hidden automatically.
- `save_recipe`: Keep a recipe in the cook's Saved list (My Kitchen on the website), or take it off with saved: false. Use when the cook says "save this", "keep that one", "add it to my favorites", or "take the chili off my saved". Saving twice is harmless. Returns the recipe link and where Saved lives.
- `search_recipes`: Find recipes on Befana by keywords, ingredients, time or diet. Use when the cook asks "what's for dinner?", "something vegetarian under 30 minutes", "a good banana bread", "something with the spinach I have", or "show me my chili" (mine: true for their own, private ones included). The cook's allergies, diet and avoid list already apply, and their own recipes come first. Returns short summaries with slugs and urls; get_recipe has the full recipe. When the cook names a recipe their preferences hide, it comes back in hidden with why: don't stop to ask; go on with that slug, tell them why it was hidden before anything else, and never present it as safe. Works signed out (public recipes).
- `suggest_from_pantry`: Recipes ranked by how much the cook already has, each with what's missing ("You have 7 of 9. Missing: lemon, parmesan."). Use when the cook asks "what can I make?", "what can I do with chicken and rice?", or "the chicken has to get used tonight" (must_use). Uses their saved pantry; signed out, or for "what if I had…", pass pantry. Staples are assumed; allergies, diet and avoid list apply; keywords, tags and max_minutes narrow it. Read the top few with the have/missing line and the url; a list of just the missing items is the natural next step.
- `update_meal_plan`: Change the cook's saved meal plan in place: swap a day for another pick (constraints: faster, max_minutes, tags, query, or a slug the cook chose), drop a day, or add one, keeping their other days. Use when the cook says "swap Tuesday for something faster", "not the salmon", "we're out Thursday", "add one more dinner". Pass plan_id from plan_meals. Returns the whole plan by day, what changed, and the same list (same id and link), prep order, swaps, nutrition, cost and say, all recomputed. A dinner swapped out counts against it in later plans. Say what changed and the list line, then ask the one question in next_steps.
- `update_recipe`: Change the cook's own recipe or version. Use when the cook says "add more garlic to my version", "make mine private", "take it down" (unpublished: true; off Befana for everyone but them, reversible; a recipe others have cooked or saved can only come down this way), "use my photo for the cover", "undo that last change", or "I made it tonight, took about 50 minutes" (tested; ask for the time if they didn't say, never assume). Pass only what changes; ingredients or steps, if passed, are the complete new list. photo: only one the cook took, never generated, stock or found; even when asked, name the recipe and get a yes first. Before calling, show the cook the changed ingredients and steps and get a yes; never save silently. Every edit keeps a revision (restore_revision: n undoes edit n). Not the cook's? Use fork_recipe.
- `update_shopping_list`: Change a saved list after the cook answers what build_shopping_list or plan_meals set aside as likely_have, or says how the trip went. remove: things they have (they come off, and count as left off); need: set-aside things they're out of (they move to the buy aisles); add: anything else for the trip, as they said it; outcomes: what happened at the store per item (bought, skipped, bought_elsewhere with the store they name). Use when the cook says "I have the flour and oil", "I'm out of chili flakes" or "skipped the salmon, got the bread at the bakery". Changes only this list, never the pantry: ask "Want me to remember these for next time?" first, then call pantry. Returns the pared list, its estimate and the order offer.