Sous Chef
REMOTE · MCP.MYSOUSCHEF.APP
Save, import and edit recipes as interactive cards in ChatGPT and Claude, synced to your iPhone.
Available components
Last scanned (6 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 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 Security46
- 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). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 421, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability78
- 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 980 tokens (~81/item across 12 items; 11 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 4% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 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
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.
- 5 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 4 Nov 26 58
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 5 Nov 2026 · Probed https://mcp.mysouschef.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mysouschef.app | CN=WE1,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 88ffd1e20ae1b47c135de2904f112bf7 |
| SANs: mysouschef.app, mcp.mysouschef.app, *.mcp.mysouschef.app | ||||||
| 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 mcp.mysouschef.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| mysouschef.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.mysouschef.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.mysouschef.app/mcp | Inconclusive | 421 |
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 →
add_recipe Add Recipe ~166
Creates a NEW recipe in your library only when the user explicitly asks to save/add it or taps Save in the recipe card. For a newly generated recipe the user has not chosen to keep, use display_recipe instead. Does not update existing recipes — to change a saved recipe use update_recipe. To make cooking-time tweaks use apply_recipe_patches. The server mints the stored import-* or ai-* recipe id; any caller-supplied recipe.id is treated only as source payload and is not used for upsert.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | – | Opaque client retry token. Reuse it only for retries of the same create request; otherwise omit it. |
| recipe | object | yes | – |
| sourceKind | string | – | – |
| sourceUrl | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
apply_recipe_patches Apply Recipe Patches ~106
Validate and apply explicit edits. Pass recipeId for a persisted cooking session, or pass the full recipe payload from display_recipe to edit an unsaved card without persistence. Does NOT modify the saved recipe in your library.
| Name | Type | Req | Description |
|---|---|---|---|
| editLabel | string | – | – |
| measurementSystem | string | – | – |
| patches | array | yes | – |
| recipe | object | – | – |
| recipeId | string | – | – |
| reply | string | – | – |
| sessionId | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
delete_recipe Delete Recipe ~38
Permanently delete a recipe owned by the authenticated user from their Sous Chef library. This cannot delete public catalog recipes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
display_recipe Display Recipe ~112
Presents a complete recipe in Sous Chef's interactive recipe card (servings, ingredients, steps, cooking mode, validated edits, Undo). Prefer this over plain chat formatting whenever you generate, retrieve, or substantially revise a full recipe — including ordinary requests like 'give me a vegan mushroom carbonara' or 'make a quick dinner for two'. Displaying is temporary: it renders the card without saving it or creating a cooking session; saving only happens through add_recipe when the user asks.
| Name | Type | Req | Description |
|---|---|---|---|
| recipe | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_recipe Get Recipe ~41
Returns the saved canonical recipe from your library or the public catalog. In-progress cooking edits live in sessions and are not returned here.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
health_check Health Check ~17
Confirm the Sous Chef MCP server is reachable.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_my_recipes List My Recipes ~43
List the authenticated user's saved Sous Chef recipes. Use this before editing when the user refers to a recipe by name instead of id.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
revert_recipe_edit Revert Recipe Edit ~105
Drop a patch group by requestId. Pass recipeId/sessionId for persisted edits, or pass the displayed card's baseRecipe and remaining patch history for a pure unsaved-card Undo. Unknown requestIds are idempotent no-ops.
| Name | Type | Req | Description |
|---|---|---|---|
| baseRecipe | object | – | – |
| measurementSystem | string | – | – |
| patches | array | – | – |
| recipeId | string | – | – |
| sessionId | string | – | – |
| targetRequestId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
set_measurement_system Set Measurement System ~73
Set measurements without ingredient patches. Pass recipeId for saved session state, or pass the full recipe payload from display_recipe to update an unsaved card without persistence.
| Name | Type | Req | Description |
|---|---|---|---|
| measurementSystem | string | yes | – |
| recipe | object | – | – |
| recipeId | string | – | – |
| sessionId | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
share_recipe Share Recipe ~99
Creates (or refreshes) a public Sous Chef link for a recipe and returns the URL. Only call when the user explicitly asks to share a recipe. The page is public, anyone with the link can view it, and it is indexed by search engines; the link shows the recipe as it currently looks, including Sous Chef edits, and sharing again updates the same link. Requires a signed-in Sous Chef account.
| Name | Type | Req | Description |
|---|---|---|---|
| recipeId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_recipe Update Recipe ~83
Deliberately updates allowed fields on a saved recipe in your library. Supports title, subtitle, summary, description, images, meta, and notes only; images and notes replace the whole array. Does not change ingredients or steps — use apply_recipe_patches for cooking-time edits in a session snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| patch | object | yes | – |
| recipeId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Sous Chef MCP server?
Sous Chef is a hosted endpoint at https://mcp.mysouschef.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 · mcp.mysouschef.app
claude mcp add --transport http app-mysouschef-sous-chef 'https://mcp.mysouschef.app/mcp'
What is the Sous Chef MCP server?
Sous Chef is an MCP server listed in the public MCP registry as app.mysouschef/sous-chef. Save, import and edit recipes as interactive cards in ChatGPT and Claude, synced to your iPhone. This page covers its hosted endpoint (https://mcp.mysouschef.app/mcp).
Is the Sous Chef MCP server safe to use?
Sous Chef scores 59 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 Sous Chef MCP server expose?
Sous Chef exposes 11 tools: health_check, list_my_recipes, display_recipe, get_recipe, add_recipe, and 6 more. Their descriptions and schemas cost roughly 883 tokens of context every time the server is loaded.
Does the Sous Chef MCP server require authentication?
No. We connected to Sous Chef without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sous Chef MCP server still maintained?
Sous Chef is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.