# Brie — Recipe MCP, Meal Plans & Groceries (remote · api.withbrie.app)

Save and adapt recipes, plan household dinners for review, and manage shared grocery lists.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `api.withbrie.app`: 65/100 (this document), [markdown](https://verifymcp.io/servers/app-withbrie-brie/api.md), [page](https://verifymcp.io/servers/app-withbrie-brie/api)

## Channel facts

- Endpoint: `https://api.withbrie.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_recipe).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 77/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 20% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http app-withbrie-brie 'https://api.withbrie.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-withbrie-brie": {
      "url": "https://api.withbrie.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-withbrie-brie": {
      "type": "http",
      "url": "https://api.withbrie.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-withbrie-brie]
url = "https://api.withbrie.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-withbrie-brie": {
      "type": "remote",
      "url": "https://api.withbrie.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-withbrie-brie --url 'https://api.withbrie.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-withbrie-brie:
    url: "https://api.withbrie.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-withbrie-brie": {
      "Transport": "http",
      "Url": "https://api.withbrie.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-withbrie-brie -t streamable-http -u 'https://api.withbrie.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-withbrie-brie": {
      "type": "http",
      "url": "https://api.withbrie.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 65, +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.

### 2026-10-20 (score 64, +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.

### 2026-10-18 (score 63, +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.

### 2026-10-16 (score 62, +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.

### 2026-10-14 (score 61, +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.

### 2026-10-13 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (13)

### `search_recipes` (~48 tokens)

Search Brie recipes

Search the connected household's saved recipes. Returns matches with sources and saved version IDs. Use get_recipe for ingredients and directions.

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `result` (object)
- `schema_version` (string)

### `get_recipe` (~87 tokens)

Read a Brie recipe

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.

Input parameters:

- `recipe_id` (string, required)
- `version_id` (string)

Output parameters:

- `result` (object)
- `schema_version` (string)

### `import_recipe` (~135 tokens)

Import a recipe into Brie

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.

Input parameters:

- `creator` (string)
- `operation_id` (string, required): 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)

Output parameters:

- `result` (object)
- `schema_version` (string)

### `get_import_status` (~51 tokens)

Check a Brie import

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.

Input parameters:

- `job_id` (string, required)

Output parameters:

- `result` (object)
- `schema_version` (string)

### `create_recipe` (~201 tokens)

Save a new recipe to Brie

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.

Input parameters:

- `cook_minutes` (integer, required)
- `cuisine` (string)
- `description` (string)
- `difficulty` (string, required)
- `ingredients` (array, required)
- `instructions` (array, required)
- `meal_types` (array, required)
- `operation_id` (string, required): 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, required)
- `servings` (integer, required)
- `tags` (array)
- `title` (string, required)

Output parameters:

- `result` (object)
- `schema_version` (string)

### `update_recipe` (~334 tokens)

Update a saved Brie recipe

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.

Input parameters:

- `change_summary` (string, required)
- `cook_minutes` (integer, required)
- `description` (string, required)
- `difficulty` (string, required)
- `expected_revision` (string, required): Copy version_revision from that same get_recipe result. On conflict, reload and review with the user; never silently overwrite.
- `expected_version_id` (string, required): The current version_id returned by get_recipe before discussing this edit.
- `ingredients` (array, required)
- `instructions` (array, required)
- `operation_id` (string, required): 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, required)
- `recipe_id` (string, required)
- `servings` (integer, required)
- `title` (string, required)
- `version_label` (string): A short descriptive name, such as Less sweet. Use the version label requested by the user, if any.

Output parameters:

- `result` (object)
- `schema_version` (string)

### `add_grocery_item` (~70 tokens)

Add a grocery item

Add a grocery item to the connected household's private grocery list in Brie.

Input parameters:

- `item` (string, required)
- `operation_id` (string, required): 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.

Output parameters:

- `result` (object)
- `schema_version` (string)

### `get_grocery_list` (~76 tokens)

Read Brie groceries

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.

Input parameters:

- `include_checked` (boolean)
- `limit` (integer)
- `offset` (integer)
- `scope` (string)

Output parameters:

- `result` (object)
- `schema_version` (string)

### `get_planning_context` (~44 tokens)

Read household planning preferences

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.

Output parameters:

- `result` (object)
- `schema_version` (string)

### `get_meal_plan` (~59 tokens)

Read a Brie week

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.

Input parameters:

- `week_start` (string, required)

Output parameters:

- `result` (object)
- `schema_version` (string)

### `propose_meal_plan` (~168 tokens)

Prepare a meal plan for review

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.

Input parameters:

- `expected_revision` (integer, required)
- `meals` (array, required)
- `operation_id` (string, required): 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, required)
- `week_start` (string, required)

Output parameters:

- `result` (object)
- `schema_version` (string)

### `get_plan_proposal` (~85 tokens)

Read a meal plan proposal

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.

Input parameters:

- `proposal_id` (string, required): 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.

Output parameters:

- `result` (object)
- `schema_version` (string)

### `approve_meal_plan` (~189 tokens)

Save an approved meal plan

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.

Input parameters:

- `operation_id` (string, required): 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, required): 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, required)

Output parameters:

- `result` (object)
- `schema_version` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-withbrie-brie/api#diagnostics

## Score history

- 2026-10-23: 65
- 2026-10-22: 64
- 2026-10-21: 64
- 2026-10-20: 64
- 2026-10-19: 63
- 2026-10-18: 63
- 2026-10-17: 62
- 2026-10-16: 62
- 2026-10-15: 61
- 2026-10-14: 61
- 2026-10-13: 60
- 2026-10-12: 60

## Common questions

### 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.

## Links

- Remote endpoint: https://api.withbrie.app/mcp
- Website: https://withbrie.app/agents
- Changelog RSS feed: https://verifymcp.io/servers/app-withbrie-brie/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-withbrie-brie/api.json
- HTML version of this page: https://verifymcp.io/servers/app-withbrie-brie/api