Recipes Daily
com.recipes-daily/recipes · 1.4.0
Search recipes and cooking guides on recipes-daily.com, or find recipes from ingredients you have.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://recipes-daily.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 4 tools.
- Protocol
- 2025-06-18
- Calls itself
- Recipes Daily 1.4.0
- Handshake time
- 622 ms
- HTTP status
- 200
The tools it lists (4, as of 27 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
search_recipesFind 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
find_recipes_by_ingredientsGiven 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.
show_recipesDraw 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.
read_guideRead 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.recipes-daily/recipes, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 9 days ago. The registry entry · recipes-daily.com