Brie — Recipe MCP, Meal Plans & Groceries
REMOTE · API.WITHBRIE.APP
Save and adapt recipes, plan household dinners for review, and manage shared grocery lists.
Available components
Last scanned (19 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 23 Oct 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 Security57
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1840 tokens (~141/item across 13 items; 13 tools + 0 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% 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
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
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 23 Oct 2026 · Probed https://api.withbrie.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.withbrie.app | CN=YE1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6e3e5482da58c93d1bd425bc879bb21e264 |
| SANs: api.withbrie.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.withbrie.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| withbrie.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://api.withbrie.app/mcp | Verified | 200 | |
| http (plaintext) | http://api.withbrie.app/mcp | HTTPS enforced | 301 | https://api.withbrie.app/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 →
add_grocery_item Add a grocery item ~70
Add a grocery item to the connected household's private grocery list in Brie.
| Name | Type | Req | Description |
|---|---|---|---|
| item | string | yes | – |
| operation_id | string | yes | A unique ID for this user-requested action. Reuse this exact ID and payload after a timeout; use a new ID only for a new action. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
approve_meal_plan Save an approved meal plan ~189
Save the exact proposal only after the user has reviewed all meals and asks to save. Copy proposal_id and review_token from that proposal. Atomically updates the specified meal groups and rebuilds canonical groceries; unmentioned meals and manual groceries remain. Can replace dishes in existing groups. A stale week or expired proposal requires a new read and user review. Retry with identical operation_id and input after a timeout. Does not buy groceries, edit recipes, or compile a combined party timeline.
| Name | Type | Req | Description |
|---|---|---|---|
| operation_id | string | yes | A unique ID for this user-requested action. Reuse this exact ID and payload after a timeout; use a new ID only for a new action. |
| proposal_id | string | yes | A unique ID for this user-requested action. Reuse this exact ID and payload after a timeout; use a new ID only for a new action. |
| review_token | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
create_recipe Save a new recipe to Brie ~201
Save a complete new recipe only after the user asks to save it. Supply ingredients, servings, times, and ordered directions; keep unknown, qualitative, or ranged quantities null and preserve their wording in raw_text. Never invent source facts or macros. Returns the saved recipe immediately; external services prepare its image and optional estimated nutrition in the background. Use get_recipe to check readiness.
| Name | Type | Req | Description |
|---|---|---|---|
| cook_minutes | integer | yes | – |
| cuisine | string | – | – |
| description | string | – | – |
| difficulty | string | yes | – |
| ingredients | array | yes | – |
| instructions | array | yes | – |
| meal_types | array | yes | – |
| operation_id | string | yes | A unique ID for this user-requested action. Reuse this exact ID and payload after a timeout; use a new ID only for a new action. |
| prep_minutes | integer | yes | – |
| servings | integer | yes | – |
| tags | array | – | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
get_grocery_list Read Brie groceries ~76
Read the connected household's grocery list. shop-now covers Upcoming; all-planned includes future planned meals. Returns paginated results; follow next_offset until null to retrieve the complete list.
| Name | Type | Req | Description |
|---|---|---|---|
| include_checked | boolean | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| scope | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
get_import_status Check a Brie import ~51
Check an import job by ID. Report its status; if it needs more information, direct the user to the import in Brie. Poll this job rather than importing again.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
get_meal_plan Read a Brie week ~59
Read the selected Monday-start week, revision, meal group and dish references, exact saved versions and sources. A missing week is an empty read, never automatic generation. Keep revision for propose_meal_plan.
| Name | Type | Req | Description |
|---|---|---|---|
| week_start | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
get_plan_proposal Read a meal plan proposal ~85
Read a proposal created by this person for this household through this OAuth client. Check its status and display the exact meals and review token before asking to save. Reading does not apply it.
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | string | yes | A unique ID for this user-requested action. Reuse this exact ID and payload after a timeout; use a new ID only for a new action. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
get_planning_context Read household planning preferences ~44
Read shared household servings, food preferences, allergies and planning window. Does not include personal nutrition logs or change preferences. Confirm this week's needs with the user before choosing meals.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
get_recipe Read a Brie recipe ~87
Read a recipe from the connected household, including ingredients, directions, and source. Supply version_id for a specific saved version or omit it for the current recipe. Display display_text as the current ingredient wording; raw_text is original source wording. Keep version_id, version_revision, and ingredient_id values for update_recipe.
| Name | Type | Req | Description |
|---|---|---|---|
| recipe_id | string | yes | – |
| version_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
import_recipe Import a recipe into Brie ~135
Import a public recipe URL or supplied recipe text when the user asks to save it, preserving its creator and source. Returns a background job; check it with get_import_status. Use create_recipe for a new recipe developed in the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| creator | string | – | – |
| operation_id | string | yes | A unique ID for this user-requested action. Reuse this exact ID and payload after a timeout; use a new ID only for a new action. |
| publication | string | – | – |
| servings | integer | – | – |
| text | string | – | – |
| title | string | – | – |
| url | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
propose_meal_plan Prepare a meal plan for review ~168
Prepare a private proposal for one week or a multi-course dinner party menu using approved saved recipes and exact version IDs. The connected assistant chooses dishes after reading preferences and ingredients. Does not save the shared calendar or groceries. Preserve unmentioned meals. Reuse group_id and retained dish_id only for a user-requested edit. Show dates, portions, sources and replacements to the user; never claim the proposal is saved. Expires after 24 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_revision | integer | yes | – |
| meals | array | yes | – |
| operation_id | string | yes | A unique ID for this user-requested action. Reuse this exact ID and payload after a timeout; use a new ID only for a new action. |
| summary | string | yes | – |
| week_start | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
search_recipes Search Brie recipes ~48
Search the connected household's saved recipes. Returns matches with sources and saved version IDs. Use get_recipe for ingredients and directions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
update_recipe Update a saved Brie recipe ~334
Update an existing recipe as a named version only after the user reviews the changes and asks to save them. First use get_recipe; copy version_id and version_revision into the expected fields. Submit the complete revised recipe: omitted ingredients and directions are removed. Map existing ingredient_id values to source_ingredient_id; use null for new ingredients. Keep current display_text and preserve qualitative or ranged quantities as null. Retains the recipe ID, image, source, earlier versions, and versions used by planned meals. External services may prepare optional nutrition and search updates. On version_conflict, read and review again before a new operation; never silently rebase or create a duplicate.
| Name | Type | Req | Description |
|---|---|---|---|
| change_summary | string | yes | – |
| cook_minutes | integer | yes | – |
| description | string | yes | – |
| difficulty | string | yes | – |
| expected_revision | string | yes | Copy version_revision from that same get_recipe result. On conflict, reload and review with the user; never silently overwrite. |
| expected_version_id | string | yes | The current version_id returned by get_recipe before discussing this edit. |
| ingredients | array | yes | – |
| instructions | array | yes | – |
| operation_id | string | yes | A unique ID for this user-requested action. Reuse this exact ID and payload after a timeout; use a new ID only for a new action. |
| prep_minutes | integer | yes | – |
| recipe_id | string | yes | – |
| servings | integer | yes | – |
| title | string | yes | – |
| version_label | string | – | A short descriptive name, such as Less sweet. Use the version label requested by the user, if any. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| schema_version | string | yes | – |
No examples provided.
How do I install the Brie — Recipe MCP, Meal Plans & Groceries server?
Brie — Recipe MCP, Meal Plans & Groceries is a hosted endpoint at https://api.withbrie.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 · api.withbrie.app
claude mcp add --transport http app-withbrie-brie 'https://api.withbrie.app/mcp'
What is the Brie — Recipe MCP, Meal Plans & Groceries server?
Brie — Recipe MCP, Meal Plans & Groceries is listed in the public MCP registry as app.withbrie/brie. Save and adapt recipes, plan household dinners for review, and manage shared grocery lists. This page covers its hosted endpoint (https://api.withbrie.app/mcp).
Is the Brie — Recipe MCP, Meal Plans & Groceries server safe to use?
Brie — Recipe MCP, Meal Plans & Groceries scores 65 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 Brie — Recipe MCP, Meal Plans & Groceries server expose?
Brie — Recipe MCP, Meal Plans & Groceries exposes 13 tools: search_recipes, get_recipe, import_recipe, get_import_status, create_recipe, and 8 more. Their descriptions and schemas cost roughly 1,547 tokens of context every time the server is loaded.
Does the Brie — Recipe MCP, Meal Plans & Groceries server require authentication?
No. We connected to Brie — Recipe MCP, Meal Plans & Groceries without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Brie — Recipe MCP, Meal Plans & Groceries server still maintained?
Brie — Recipe MCP, Meal Plans & Groceries is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.