Recipes Daily
REMOTE · RECIPES-DAILY.COM
Search recipes and cooking guides on recipes-daily.com, or find recipes from ingredients you have.
Available components
Last scanned (21 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Entertainment and Games
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1192 tokens (~238/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_recipes” rewrote its description, which is the text the model reads security
- Schema quality: 905 → 1192 ▼ functional
- Server version: 1.2.0 → 1.4.0 functional
- New tool “read_guide” functional
- “search_recipes” reworded the description of “query” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Aug 26 0
- Resource “recipe-cards-app” now points somewhere else: ui://resources/recipe-cards-app → ui://resources/recipe-cards-app-44358a8e security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_recipes” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.2.0 functional
- New tool “find_recipes_by_ingredients” functional
- New tool “show_recipes” functional
- 20 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fail → pass ▲ functional
- First check of Capabilities: pass functional
- First check of Schema quality: 100 functional
- Schema quality: excellent → good functional
- New resource “recipe-cards-app” functional
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 6 Nov 2026 · Probed https://recipes-daily.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=recipes-daily.com | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 53a3e8e4067909ee134eceb296759802 |
| SANs: recipes-daily.com, *.recipes-daily.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of recipes-daily.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| recipes-daily.com. | No DS | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recipes-daily.com/mcp | Verified | 200 | |
| http (plaintext) | http://recipes-daily.com/mcp | HTTPS enforced | 301 | https://recipes-daily.com/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 →
find_recipes_by_ingredients Find recipes by ingredients on hand ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ingredients | array | – | What is on hand, one ingredient per entry — e.g. ["broccoli", "chicken breast", "lemon"]. |
| limit | integer | – | Recipes to return, ranked by coverage. |
No output schema declared.
No examples provided.
read_guide Read a cooking guide ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guide | string | – | The guide to read, as the absolute recipes-daily.com URL search_recipes returned — e.g. "https://recipes-daily.com/guides/preparations/why-do-dried-beans-take-so-long-to-cook". |
No output schema declared.
No examples provided.
search_recipes Search recipes ~261
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page. |
| page | integer | – | 1-based. The response names the next page when there is one. |
| query | string | – | What to search for. Recipes are matched on titles and descriptions, so a word or short phrase matches better than a full question, and there are no boolean operators. Omit it to list every recipe, ne… |
No output schema declared.
No examples provided.
show_recipes Show recipes as cards ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| recipes | array | – | The recipes to draw, as absolute recipes-daily.com URLs — e.g. ["https://recipes-daily.com/make/chicken-piccata-pan-fried-25-minute"]. A bare slug works too. Order is kept, so put the strongest recom… |
No output schema declared.
No examples provided.
How do I install the Recipes Daily MCP server?
Recipes Daily is a hosted endpoint at https://recipes-daily.com/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 · recipes-daily.com
claude mcp add --transport http com-recipes-daily-recipes 'https://recipes-daily.com/mcp'
What is the Recipes Daily MCP server?
Recipes Daily is an MCP server listed in the public MCP registry as com.recipes-daily/recipes. Search recipes and cooking guides on recipes-daily.com, or find recipes from ingredients you have. This page covers its hosted endpoint (https://recipes-daily.com/mcp).
Is the Recipes Daily MCP server safe to use?
Recipes Daily scores 88 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 Recipes Daily MCP server expose?
Recipes Daily exposes 4 tools: search_recipes, find_recipes_by_ingredients, show_recipes, read_guide. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.
Does the Recipes Daily MCP server require authentication?
No. We connected to Recipes Daily without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Recipes Daily MCP server still maintained?
Recipes Daily is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Recipes Daily MCP server?
VerifyMCP ran 14 checks on Recipes Daily, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.