# Recipes Daily

> Search recipes and cooking guides on recipes-daily.com, or find recipes from ingredients you have.

- name: com.recipes-daily/recipes
- version: 1.4.0
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 85/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.recipes-daily%2Frecipes
- tools: https://api.protogrid.dev/v1/servers/com.recipes-daily%2Frecipes/tools

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

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "recipes": {
      "type": "http",
      "url": "https://recipes-daily.com/mcp"
    }
  }
}
```


## Trust

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

## Quality 85/100 (good)

### 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`: 4 of 4 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: find_recipes_by_ingredients (destructiveHint, openWorldHint); show_recipes (destructiveHint, openWorldHint); read_guide (destructiveHint, openWorldHint); …
- pass `tools.token_cost`: about 1,001 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 2 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

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

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

- tools: 4, about 1,001 tokens to load them all
- tool set hash: c3831632ef20bdac52824bb7e5c16242
- tools last changed: 2026-09-29T04:13:09.647Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.recipes-daily/recipes.svg)](https://protogrid.dev/servers/com.recipes-daily/recipes)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-09-29 `read_guide` added
  - Read 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.
- 2026-09-29 `search_recipes` changed (description, inputSchema)
  - before: Find 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 URL, description, total time, servings and categories — so candidates can be ruled out without opening them.
  - after: Find 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 URL, description, total time, servings and categories — so candidates can be ruled out without opening them. The first page also lists matching cooking guides, for how and why questions about technique, storage and substitutions; read one in full with read_guide.

Full history: https://api.protogrid.dev/v1/servers/com.recipes-daily%2Frecipes/changes

## Remotes

- https://recipes-daily.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.9279279)

## Packages

_none_

## Tools (4)

- `find_recipes_by_ingredients`: Given 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.
- `read_guide`: Read 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.
- `search_recipes`: Find 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 URL, description, total time, servings and categories — so candidates can be ruled out without opening them. The first page also lists matching cooking guides, for how and why questions about technique, storage and substitutions; read one in full with read_guide.
- `show_recipes`: Draw 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.