# Bryti (remote · api.bryti.app)

Plan dinners with Bryti from your own assistant: the week, shopping list, pantry and recipes.

- Trust score: 89/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Endpoint: `https://api.bryti.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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-11-21.

- **Endpoint Security**: 100/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 8494 tokens (~143/item across 59 items; 59 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 60 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 Bryti MCP server?

Bryti is a hosted endpoint at https://api.bryti.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-bryti-bryti 'https://api.bryti.app/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "app-bryti-bryti": {
      "type": "http",
      "url": "https://api.bryti.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-11-21 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 88, +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-11-18 (score 87, 0)

- [cosmetic] “update_household_settings” added an optional parameter “saveGeneratedRecipes”

### 2026-11-17 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 85, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “save_recipe” rewrote its description, which is the text the model reads
- [security] Tool “set_household_language” rewrote its description, which is the text the model reads
- [cosmetic] “save_recipe” added an optional parameter “language”
- [cosmetic] “update_household_settings” added an optional parameter “weekStartsOn”
- [cosmetic] “adapt_dinner_ingredient” reworded the description of “insteadOfFood”
- [cosmetic] “adapt_dinner_ingredient” reworded the description of “useFood”
- [cosmetic] “edit_recipe” reworded the description of “timeline”
- [cosmetic] “get_shopping_guide” reworded the description of “store”
- [cosmetic] “save_recipe” reworded the description of “timeline”
- [cosmetic] “set_category_for_date” reworded the description of “strength”
- [cosmetic] “set_max_cooking_time_for_date” reworded the description of “strength”
- [cosmetic] “update_household_settings” reworded the description of “pantryWeight”
- [cosmetic] “upsert_category_excluded_days_rule” reworded the description of “strength”
- [cosmetic] “upsert_category_frequency_rule” reworded the description of “strength”
- [cosmetic] “upsert_category_on_day_rule” reworded the description of “strength”
- [cosmetic] “upsert_max_cooking_time_rule” reworded the description of “strength”
- [cosmetic] “upsert_max_total_time_rule” reworded the description of “strength”
- [cosmetic] “upsert_price_class_rule” reworded the description of “strength”
- [cosmetic] “upsert_repeat_after_days_rule” reworded the description of “strength”
- [cosmetic] Tool “set_recipe_favorite” changed its title: Mark a favourite recipe → Mark a favorite recipe

### 2026-11-12 (score 85, +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-11-11 (score 84, 0)

- [functional] New tool “set_lunchbox_portions”
- [cosmetic] “update_household_settings” added an optional parameter “lunchboxWeekdayPortions”

## MCP tools (59)

### `get_household_overview` (~36 tokens)

Household

Read the household's name, language and usual dinner time, who lives in it, their dietary constraints and their food preferences.

### `get_rules` (~29 tokens)

Meal rules

Read the household's meal rules, and the national defaults that apply while it has none of its own.

### `get_week_plan` (~101 tokens)

Week plan

Read the dinner plan for the week starting at weekStart (a Monday), one page of days at a time.

Input parameters:

- `cursor` (string): The `nextCursor` of the page before — the date that page stopped at; omit for the first page.
- `limit` (integer): Days per page, 1-31; the whole week when omitted.
- `weekStart` (string, required): Monday of the week, ISO date (yyyy-MM-dd).

### `get_inventory` (~133 tokens)

Pantry

Read what the household has at home: pantry, fridge and freezer, filtered and paged.

Input parameters:

- `cursor` (string): The `nextCursor` of the page before; omit for the first page.
- `group` (string): Only this section: UseSoon (should be used up), LikelyAvailable, Uncertain (nobody has confirmed it), Aged (the archive).
- `limit` (integer): Rows per page, 1-100; 40 when omitted.
- `place` (string): Only this storage location.
- `query` (string): A food to look for; omit for everything.

### `get_shopping_list` (~89 tokens)

Shopping list

Read the shopping list for the week starting at weekStart, or the current week without one: the week's dinners minus what is at home. The guide for putting it in an online store's cart is get_shopping_guide, and the shop_online prompt.

Input parameters:

- `weekStart` (string): Monday of the week, ISO date (yyyy-MM-dd). Leave it out for the current week.

### `get_stores` (~17 tokens)

Stores

Read the stores the household shops in.

### `get_recipes` (~145 tokens)

Recipes

Search or list the household's recipes, paged; a search and the favourites also cover the shared starter library.

Input parameters:

- `category` (string): Only dinners of this category.
- `cursor` (string): The `nextCursor` of the page before; omit for the first page.
- `favourites` (boolean): Only the dishes the household has marked as favourites, its own and the starter library's.
- `limit` (integer): Recipes per page, 1-100; 40 when omitted.
- `query` (string): A dish or ingredient to look for. Also searches the shared starter library and the household's base recipes, neither of which is listed without it.

### `get_recipe` (~37 tokens)

Recipe

Read one recipe by id: ingredients, steps and times.

Input parameters:

- `recipeId` (string, required): Id of the recipe, from get_recipes.

### `get_day` (~68 tokens)

Day overview

Read one day: the dinner, its time, the calendar, meal events and the rules that apply.

Input parameters:

- `date` (string, required): The day asked about, ISO date (yyyy-MM-dd) — resolve «tirsdag» to the nearest Tuesday from today, «i morgen» to tomorrow.

### `get_planned_dinner` (~39 tokens)

Planned dinner

Read the planned dinner and its recipe for one date.

Input parameters:

- `date` (string, required): The dinner date, ISO date (yyyy-MM-dd).

### `get_meal_events` (~121 tokens)

Guests and meals out

Read the household's meal events (guests, eating out, packed lunches) between two dates.

Input parameters:

- `cursor` (string): The `nextCursor` of the page before; omit for the first page.
- `from` (string): First day to read, ISO date; defaults to today.
- `limit` (integer): Events per page, 1-100; 50 when omitted.
- `to` (string): Last day to read, ISO date; defaults to 30 days after 'from'. At most 92 days after it.

### `search_help` (~59 tokens)

Help articles

Search Bryti's help articles.

Input parameters:

- `language` (string): 'nb' or 'en' — the language of the question; defaults to the household's.
- `query` (string, required): The question, in the household's own words and language.

### `search_tips` (~67 tokens)

Kitchen tips

Search Bryti's fact-checked kitchen tips.

Input parameters:

- `query` (string, required): The cooking question in a few words, in the household's own language — the food and what happened or what they want to do («gryte for salt», «steak rest», «freeze potatoes»).

### `get_calendar_events` (~68 tokens)

Calendar

Read the household's calendar events between two dates.

Input parameters:

- `from` (string): First day to read, ISO date (yyyy-MM-dd); defaults to today.
- `to` (string): Last day to read, ISO date (yyyy-MM-dd); defaults to 14 days after 'from'.

### `get_shopping_guide` (~103 tokens)

Shopping guide

Returns Bryti's guide, in the household's language, for putting the household's shopping list in an online store's basket. The member places the order.

Input parameters:

- `store` (string, required): The store: oda, meny, or other for any other online grocery store. A named store gets its own note only when it is in the household's country; any other store gets the general guide. «annen» is the o…

### `get_planning_status` (~84 tokens)

Planning status

How a planning run started by plan_week or replan_open_days is going: queued, running, done or failed, and how many days the week has planned once it is done. Without jobId, the household's latest run.

Input parameters:

- `jobId` (string): The jobId plan_week or replan_open_days answered with. Omit for the latest run.

### `add_shopping_item` (~131 tokens)

Add to shopping list

Add one item to the shopping list for the week that holds weekStart. The week needs a plan.

Input parameters:

- `displayName` (string, required): What to buy, e.g. 'melk' or 'kaffe'. Include the amount in quantity/unit rather than in the name.
- `quantity` (number): Amount, if the user said one, e.g. 2.
- `unit` (string): Unit for the quantity, e.g. 'l', 'stk', 'g'; omit if none.
- `weekStart` (string, required): Any date in the week whose list gets the item.

### `check_shopping_item` (~90 tokens)

Tick off a shopping item

Tick an item off the shopping list (purchased=true) or put it back (purchased=false), by its name.

Input parameters:

- `itemName` (string, required): The item's display name, e.g. 'melk'.
- `purchased` (boolean, required): true = bought it; false = back on the list.
- `weekStart` (string, required): Any date in the week whose list holds the item.

### `remove_shopping_item` (~78 tokens)

Remove from shopping list

Remove an item the household added by hand from the week's shopping list, by its name. Items the week's dinners need cannot be removed.

Input parameters:

- `itemName` (string, required): The item's name as the list shows it, e.g. 'melk'.
- `weekStart` (string, required): Any date in the week whose list holds the item.

### `add_inventory_observation` (~129 tokens)

Note food at home

Record what happened to a food at home: bought, seen, used, frozen, thrown out or gone.

Input parameters:

- `displayName` (string, required): Human-readable name, e.g. 'Salmon fillet'.
- `foodKey` (string): Leave this out: Bryti finds the food from displayName.
- `observationType` (string, required): What was observed.
- `quantity` (number): Amount, if known.
- `storageLocation` (string, required): Where it is stored.
- `unit` (string): Unit for the quantity, e.g. 'g', 'dl', 'pcs'.

### `add_guests_for_date` (~185 tokens)

Add dinner guests

Add guests for dinner on a date, or over several days with endDate. Name the household's usual guests in guestNames instead of counting them.

Input parameters:

- `adultCount` (integer, required): Number of anonymous adult guests (not counting named ones).
- `babyCount` (integer): Number of baby guests (under about two years): they eat from a parent's plate, but the dinner must be safe for them.
- `childCount` (integer, required): Number of anonymous child guests (not counting named ones).
- `date` (string, required): The dinner date (first day for a multi-day visit), ISO date.
- `endDate` (string): Last day of a multi-day visit, ISO date; omit for a single dinner.
- `guestNames` (array): Usual guests coming by name.
- `notes` (string): Optional note, e.g. 'grandparents'.

### `mark_eating_out` (~91 tokens)

Mark eating out

Mark that the household eats out on a date, or over several days with endDate. Planned dinners on unlocked days in the span are taken off the plan.

Input parameters:

- `date` (string, required): The date (first day for a span), ISO date.
- `endDate` (string): Last day of the span, ISO date; omit for a single evening.
- `notes` (string): Optional note.

### `mark_away` (~138 tokens)

Mark away from home

Mark the household away from home (a trip, the cabin) from date to endDate. Planned dinners on unlocked days in the span are taken off the plan.

Input parameters:

- `date` (string, required): First day away, ISO date. A trip lies ahead: take a bare weekday from the context line's 'nearest weekday ahead' field, never from a day marked '(past)'.
- `endDate` (string): Last day away, ISO date; omit for a single day. Never earlier than 'date' — a span runs forwards from its first day.
- `notes` (string): Optional note, e.g. 'cabin trip'.

### `set_dinner_time` (~88 tokens)

Set dinner time

Move when dinner is served on one evening (date, or today), or from now on for some weekdays.

Input parameters:

- `date` (string): The evening to move, ISO date; omit for today.
- `time` (string, required): When dinner is served, 24-hour HH:mm.
- `weekdays` (array): Make it a standing rule for these weekdays; omit for this evening only.

### `set_prep_days` (~161 tokens)

Set prep days

Set the weekdays the household preps ahead for the week, and the hour it starts. Steps a recipe allows to be done early are then shown on the latest prep day that keeps them fresh. An empty weekdays list turns prep days off. freezesPrep lets steps that keep frozen go to an earlier prep day.

Input parameters:

- `freezesPrep` (boolean): True when the household freezes what keeps frozen, so it can be made on an earlier prep day. Omit to leave it as it is.
- `time` (string): When prep starts on those days, 24-hour HH:mm. Omit to keep the hour the household has (15:00 when it has none).
- `weekdays` (array, required): The prep days. Empty turns prep days off.

### `replace_dinner` (~112 tokens)

Swap a dinner

Swap the planned dinner on a date to another dish suggested for that day, by its title. A recipe from the household's library by its exact title also works, on a day nobody has planned yet too: the week opens around it. A title that does not match fails with the dishes to choose from.

Input parameters:

- `date` (string, required): The dinner date, ISO date.
- `dishTitle` (string, required): Title of the dish to switch to: one of the day's suggestions, or a recipe in the library.

### `set_dinner_lock` (~58 tokens)

Lock or unlock a dinner

Lock a day's dinner so replanning never changes it (locked=true), or unlock it.

Input parameters:

- `date` (string, required): The dinner date, ISO date.
- `locked` (boolean, required): true = pin the dinner; false = unpin.

### `set_recipe_favorite` (~97 tokens)

Mark a favorite recipe

Mark a recipe as a favourite (favorite=true) or take the mark away, for the family or one member. Use the exact title from get_recipes.

Input parameters:

- `favorite` (boolean, required): true = mark as favorite; false = remove the mark.
- `memberName` (string): Member the favorite belongs to; omit for the whole family.
- `recipeTitle` (string, required): Exact title of the recipe, from get_recipes.

### `import_recipe_from_url` (~73 tokens)

Import a recipe from a link

Bring a recipe from a web page into the household's recipes. Bryti reads the page; this uses some of the household's monthly credits. The import reads what can be made ahead from the page itself; get_recipe shows the timeline afterwards.

Input parameters:

- `url` (string, required): The recipe page's full https address.

### `save_recipe` (~418 tokens)

Save a recipe

Save a new recipe to the household's own recipes. Mark what can be made ahead (a sauce, a dough) in timeline, so it lands on the prep day. Give language ('nb' or 'en') for the language the recipe is written in, so it is translated for a household that reads another.

Input parameters:

- `activeMinutes` (integer, required): Hands-on cooking minutes.
- `category` (string, required): The meal category.
- `equipment` (array): What the kitchen needs that is not food. Never on the shopping list. On edit_recipe the list replaces it.
- `ingredients` (array, required): The ingredients with quantities.
- `language` (string): The language the recipe's words are written in: 'nb' for Norwegian, 'en' for English. Say it whenever it is not the household's language, so Bryti can translate the recipe for its readers.
- `note` (string): The recipe's own note: the intro and the author's assessment. On edit_recipe an empty string removes it.
- `ovenSettings` (array): The oven per step. On edit_recipe the list replaces all of them.
- `portions` (integer, required): How many portions the base quantities make.
- `stepNotes` (array): Notes under the steps. On edit_recipe the list replaces all of them.
- `steps` (array, required): Ordered cooking steps.
- `tags` (array, required): Descriptive tags; may be empty.
- `timeline` (array): The steps done at a set time before serving, and the ones that can be made ahead. Mark what can be made ahead whenever the recipe or the user says so («sausen kan lages dagen før» / «the sauce can be…
- `title` (string, required): Recipe title, e.g. 'Grandma's fish soup'.
- `totalMinutes` (integer, required): Total minutes from start to serving (≥ active).

### `record_outcome` (~91 tokens)

Record how dinner went

Record how a planned dinner went: made, made with changes, not made, or eaten elsewhere.

Input parameters:

- `date` (string, required): The dinner date, ISO date.
- `notes` (string): Optional note from the user.
- `reason` (string): Why it wasn't cooked as planned; on a made dinner only DidNotLike, else omit.
- `status` (string, required): What happened to the dinner.

### `plan_week` (~260 tokens)

Plan the week

Plan dinners for a week with Bryti's planner, inside the household's rules, events, allergies and pantry. The run is queued and takes one to three minutes; the answer carries a jobId — ask get_planning_status for it. A week that already has planned dinners answers confirmation_required: ask the member, then call again with replace: true. Uses the household's monthly credits, like planning in the app. For the rest of a week that is already planned, use replan_open_days.

Input parameters:

- `allowGeneration` (integer): How many dinners Bryti may invent this week (0-7). Only when the user says so — «bare to nye retter», «ingen nye retter denne uka». Omit to use the household's own setting.
- `allowNearMisses` (boolean): Whether a day may bend a soft rule or the calendar's guessed busy-evening cap rather than stay without a dinner. Defaults to true; pass false when the user insists every rule holds even if a day ends…
- `replace` (boolean): True when the member has said yes to replacing the dinners already planned this week.
- `weekStart` (string, required): Any date in the week to plan; normalized to that week's Monday.

### `replan_open_days` (~77 tokens)

Plan the open days

Fill the open days of a week that already has a plan; dinners already planned, locked or answered stay where they are. Queued like plan_week; ask get_planning_status with the jobId. Uses the household's monthly credits.

Input parameters:

- `weekStart` (string, required): Any date in the week; resolved to that week's plan.

### `clear_week` (~127 tokens)

Clear the week

Take every dinner off a week and keep the plan, so it can be planned again at once. Days already passed and evenings out stay; a locked day stays unless includeLocked is true. The shopping list loses the recipe lines and keeps what the household added by hand. Ask the member first: only the Week page's «Angre» right after a clear in the app brings the dinners back.

Input parameters:

- `includeLocked` (boolean): True only when the household has said the locked days go too.
- `weekStart` (string, required): Any date in the week; resolved to that week's plan.

### `set_category_for_date` (~228 tokens)

Set a day's dinner category

Add a rule for one date: the dinner should be of this category (Hard = must, Soft = preferably). The answer's undo deletes the rule again.

Input parameters:

- `category` (string, required): The meal category for that day.
- `date` (string, required): The date, ISO date.
- `strength` (string, required): Soft unless the household says the rule must hold. Hard ONLY when the words are must/never/always (må/aldri/alltid/skal/kan ikke/ikke lov). Everything else is Soft — a preference the planner may bend…

### `set_max_cooking_time_for_date` (~225 tokens)

Set a day's cooking time

Add a rule for one date: at most this many active minutes at the stove. The answer's undo deletes the rule again.

Input parameters:

- `date` (string, required): The date, ISO date.
- `minutes` (integer, required): Maximum active minutes at the stove.
- `strength` (string, required): Soft unless the household says the rule must hold. Hard ONLY when the words are must/never/always (må/aldri/alltid/skal/kan ikke/ikke lov). Everything else is Soft — a preference the planner may bend…

### `delete_rule` (~88 tokens)

Delete a meal rule

Delete one of the household's own meal rules by the id get_rules shows. National defaults are not rules of the household's own and cannot be deleted. Ask the member first: the answer's undo files the rule again, except a dinner time, the prep days or a rule over a range of dates.

Input parameters:

- `ruleId` (string, required): The rule's id, as get_rules shows it.

### `set_leftover_dinners` (~53 tokens)

Turn leftover dinners on or off

Whether Bryti plans leftover dinners: about every third day, never on Friday or Saturday. A household setting, not a rule.

Input parameters:

- `enabled` (boolean, required): True to plan leftover dinners, false for never.

### `set_lunchbox_portions` (~119 tokens)

Set lunchboxes from a dinner

Set how many extra portions one planned dinner cooks for the next day's lunchboxes, 0 to 10; without portions it follows the household's weekday setting again. Lunch is not planned: the extra portions are bought and cooked with the dinner. A dish that should not be heated again makes none.

Input parameters:

- `date` (string, required): The dinner's date, yyyy-MM-dd.
- `portions` (integer): Extra portions for the next day's lunchboxes, 0–10. Leave it out to follow the household's weekday setting again.

### `edit_recipe` (~377 tokens)

Change a recipe

Change a recipe the household owns, found by its current title. Only the fields given change; ingredients, steps and timeline replace the whole list when given, so send them complete, as get_recipe shows them. Mark what can be made ahead in timeline, so it lands on the prep day.

Input parameters:

- `activeMinutes` (integer): Hands-on cooking minutes.
- `category` (string): The meal category.
- `equipment` (array): What the kitchen needs that is not food. Never on the shopping list. On edit_recipe the list replaces it.
- `ingredients` (array): The COMPLETE new ingredient list.
- `newTitle` (string): A new title, when the dish is being renamed.
- `note` (string): The recipe's own note: the intro and the author's assessment. On edit_recipe an empty string removes it.
- `ovenSettings` (array): The oven per step. On edit_recipe the list replaces all of them.
- `portions` (integer): How many portions the base quantities make.
- `recipeTitle` (string, required): The recipe's current title.
- `stepNotes` (array): Notes under the steps. On edit_recipe the list replaces all of them.
- `steps` (array): The COMPLETE new list of steps.
- `tags` (array): The complete new tag list.
- `timeline` (array): The steps done at a set time before serving, and the ones that can be made ahead. Mark what can be made ahead whenever the recipe or the user says so («sausen kan lages dagen før» / «the sauce can be…
- `totalMinutes` (integer): Total minutes from start to serving (≥ active).

### `delete_recipe` (~58 tokens)

Delete a recipe

Delete one of the household's own recipes, by its title. Built-in recipes cannot be deleted, and a recipe planned for a day ahead stays until that day has another dinner.

Input parameters:

- `title` (string, required): Exact title of the recipe to delete.

### `wish_dish` (~131 tokens)

Wish for a dish

Put a dish on the household's wish list, or add a vote when it is already there. A wish lifts the dish in the next planned week; it is a weight, never a rule. A title from get_recipes gives that recipe; any other name is kept as said.

Input parameters:

- `memberName` (string): The member the wish is for when someone wishes on a child's behalf; omit for the speaker's own wish.
- `title` (string, required): The dish: its exact cookbook title when it is in the cookbook, else the user's own words, e.g. 'pannekaker'.

### `adapt_dinner_ingredient` (~127 tokens)

Use what is at home

Make one evening's dinner with something the household has instead of an ingredient, e.g. milk instead of cream. Only that evening changes, and the replaced ingredient leaves the shopping list; the recipe in the library stays as it is.

Input parameters:

- `date` (string, required): The dinner date, ISO date.
- `insteadOfFood` (string, required): The ingredient in that dinner it replaces, e.g. «fløte» / «cream».
- `useFood` (string, required): What to use — the food the household already has, e.g. «melk» / «milk».

### `mark_member_absent` (~63 tokens)

Mark someone away for dinner

Mark that one member of the household is not home for dinner on a date, by the name get_household_overview shows.

Input parameters:

- `date` (string, required): The date, ISO date.
- `memberName` (string, required): Name of the member who is away.

### `delete_meal_event` (~83 tokens)

Remove from the dinner calendar

Remove guests, an evening out, days away or a member's absence on one date. Without eventType every entry on the date goes. A day away that is removed can be planned again.

Input parameters:

- `date` (string, required): The date whose events to remove, ISO date.
- `eventType` (string): Only remove events of this type; omit for all.

### `add_food_preference` (~141 tokens)

Note a like or dislike

Record that the household, or one member, likes or dislikes an ingredient, a dish, a category, a texture or a way of cooking. Allergies and intolerances are not likes: Bryti keeps them in the app.

Input parameters:

- `memberName` (string): Member the preference belongs to; omit for the whole household.
- `sentiment` (string, required): How strongly they feel.
- `subject` (string, required): The food, ingredient, or dish. For subjectType Taste prefer the canonical lowercase English keys: sweet, salty, sour, bitter, umami, spicy, rich, fresh.
- `subjectType` (string, required): What the subject refers to.

### `delete_food_preference` (~70 tokens)

Remove a like or dislike

Remove a recorded like or dislike, by its subject as get_household_overview shows it.

Input parameters:

- `memberName` (string): Member it belongs to; omit for a household-level preference.
- `subject` (string, required): The recorded subject, e.g. 'broccoli' or 'spicy'.

### `merge_pantry_foods` (~121 tokens)

Merge two pantry rows

Merge two pantry rows the household says are the same food. The first stops being its own row and reads as the second, which keeps its name. The food keys are the ones get_inventory gives. The household can split them again in the app.

Input parameters:

- `fromFoodKey` (string, required): Canonical lowercase key of the row that stops being its own, e.g. 'fusilli'.
- `toFoodKey` (string, required): Canonical lowercase key of the row that survives and gives the merged row its name, e.g. 'pasta'.

### `upsert_category_frequency_rule` (~251 tokens)

Set how often a category comes

Set how many times a week a meal category should be on the plan, at least and at most. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.

Input parameters:

- `category` (string, required): The meal category.
- `maximumPerWeek` (integer, required): Maximum dinners per week.
- `minimumPerWeek` (integer, required): Minimum dinners per week.
- `strength` (string, required): Soft unless the household says the rule must hold. Hard ONLY when the words are must/never/always (må/aldri/alltid/skal/kan ikke/ikke lov). Everything else is Soft — a preference the planner may bend…

### `upsert_category_excluded_days_rule` (~229 tokens)

Keep a category off some days

Set the weekdays a meal category is never planned. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.

Input parameters:

- `category` (string, required): The meal category.
- `excludedWeekdays` (array, required): Weekdays to exclude.
- `strength` (string, required): Soft unless the household says the rule must hold. Hard ONLY when the words are must/never/always (må/aldri/alltid/skal/kan ikke/ikke lov). Everything else is Soft — a preference the planner may bend…

### `upsert_category_on_day_rule` (~249 tokens)

Put a category on a weekday

Set that a meal category belongs on a weekday every week, e.g. taco on Fridays. One single date is set_category_for_date. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.

Input parameters:

- `category` (string, required): The meal category.
- `strength` (string, required): Soft unless the household says the rule must hold. Hard ONLY when the words are must/never/always (må/aldri/alltid/skal/kan ikke/ikke lov). Everything else is Soft — a preference the planner may bend…
- `weekday` (string, required): The weekday it belongs on, week after week.

### `upsert_max_cooking_time_rule` (~284 tokens)

Limit time at the stove

Set the most minutes of active cooking a dinner may take, every day or on the weekdays named. One single date is set_max_cooking_time_for_date; the time until dinner is on the table, oven included, is upsert_max_total_time_rule. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.

Input parameters:

- `minutes` (integer, required): Maximum active minutes at the stove, 5-240.
- `strength` (string, required): Soft unless the household says the rule must hold. Hard ONLY when the words are must/never/always (må/aldri/alltid/skal/kan ikke/ikke lov). Everything else is Soft — a preference the planner may bend…
- `weekdays` (array): The weekdays the maximum holds on; omit for every day.

### `upsert_max_total_time_rule` (~262 tokens)

Limit time until dinner

Set the most minutes from the first step until dinner is on the table, oven and resting included, every day or on the weekdays named. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.

Input parameters:

- `minutes` (integer, required): Maximum minutes from the first step to the table, 10-240.
- `strength` (string, required): Soft unless the household says the rule must hold. Hard ONLY when the words are must/never/always (må/aldri/alltid/skal/kan ikke/ikke lov). Everything else is Soft — a preference the planner may bend…
- `weekdays` (array): The weekdays the maximum holds on; omit for every day.

### `upsert_price_class_rule` (~269 tokens)

Keep dinners cheap

Set how dear dinners may be, every day or on the weekdays named: Cheap, or CheapOrMid. Bryti prices each dinner from store prices; there is no amount in kroner. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.

Input parameters:

- `ceiling` (string, required): The dearest class allowed: Cheap, or CheapOrMid.
- `strength` (string, required): Soft unless the household says the rule must hold. Hard ONLY when the words are must/never/always (må/aldri/alltid/skal/kan ikke/ikke lov). Everything else is Soft — a preference the planner may bend…
- `weekdays` (array): The weekdays the rule holds on; omit for every day.

### `upsert_repeat_after_days_rule` (~242 tokens)

Space out the same dish

Set how many days must pass before the same dish comes back, 3 to 30. Bryti's default is 10. A rule about the same thing is changed, not added twice. Soft unless the household says it must hold.

Input parameters:

- `days` (integer, required): Days between two servings of the same dish, 3–30.
- `strength` (string, required): Soft unless the household says the rule must hold. Hard ONLY when the words are must/never/always (må/aldri/alltid/skal/kan ikke/ikke lov). Everything else is Soft — a preference the planner may bend…

### `update_household_settings` (~565 tokens)

Change household settings

Change the household's name, time zone, usual dinner time, address (which decides the stores nearby) or how the week is planned. Only the fields given change. One evening's dinner time is set_dinner_time.

Input parameters:

- `address` (string): New address, if changing; empty string clears it.
- `alwaysNewDishes` (boolean): true makes that number a target instead of a ceiling: exactly that many new dishes every planned week, on the days the cookbook has least to offer. false only invents when the cookbook falls short.
- `defaultDinnerTime` (string): New default dinner time as HH:mm, if changing.
- `lunchboxWeekdayPortions` (integer): 0–6: how many extra portions the dinner the night before a weekday cooks for tomorrow's lunchboxes. 0 = none. One dinner's own number is set on its day card.
- `maxNewDishesPerWeek` (integer): 0–7: how many of the week's dinners Bryti may invent. The rest are taken from the household's own recipes and the built-in library. 0 = only dishes they already know.
- `name` (string): New household name, if changing.
- `pantryWeight` (string): How much the week leans on what the household already has at home. Usual: what they like and their favourites go first, the pantry breaks ties. Prefer («bruk gjerne det vi har» / «use what we have»):…
- `prefersLeftoverDinners` (boolean): true plans a leftovers evening roughly every third day, eating what the two days before cooked; false plans cooking every day.
- `saveGeneratedRecipes` (boolean): true puts every dish Bryti makes up straight into the cookbook. false (the default) leaves a new dish on its day only; the household saves the ones they want, and an unsaved one is never suggested ag…
- `timeZoneId` (string): IANA time zone id, e.g. 'Europe/Oslo', if changing. Only when the user says where they are or asks to change the zone — never guessed from the language they write in.
- `weekStartsOn` (string): The day the household's calendar starts on: Monday, or Sunday (common in the US). Sunday also names each week by its dates instead of its week number. Plans still run Monday to Sunday either way.

### `set_household_language` (~90 tokens)

Change the household's language

Set the language Bryti uses with the household: nb (Norwegian Bokmål), nn (Nynorsk) or en (English). With nn the chat writes nynorsk, while the app's screens and saved recipes stay bokmål.

Input parameters:

- `languageCode` (string, required): BCP-47 code: 'nb' (bokmål), 'nn' (nynorsk) or 'en'.

### `select_stores` (~128 tokens)

Choose stores

Set the stores the household shops at. This replaces the whole selection, so name every store they want; get_stores shows the ones chosen now. Bryti looks the names up near the household's address, and a name it does not find fails with the stores nearby.

Input parameters:

- `address` (string): Address the stores are near; omit when they are near the household's own address.
- `storeAddresses` (array): Only for an undo: the address each store was found near, in the same order as storeNames.
- `storeNames` (array, required): The stores to shop at.

### `activate_plan` (~64 tokens)

Make a week's plan live

Make the plan for the week that holds weekStart the one that counts. A plan is live as soon as it is made, so this matters only when the household asks for it.

Input parameters:

- `weekStart` (string, required): Any date in the week; resolved to that week's plan.

## Diagnostics

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

## Score history

- 2026-11-21: 89
- 2026-11-20: 88
- 2026-11-19: 88
- 2026-11-18: 87
- 2026-11-17: 87
- 2026-11-16: 86
- 2026-11-15: 86
- 2026-11-14: 85
- 2026-11-13: 85
- 2026-11-12: 85
- 2026-11-11: 84
- 2026-11-10: 84
- 2026-11-09: 83
- 2026-11-08: 83
- 2026-11-07: 40
- 2026-11-06: 40

## Common questions

### What is the Bryti MCP server?

Bryti is an MCP server listed in the public MCP registry as app.bryti/bryti. Plan dinners with Bryti from your own assistant: the week, shopping list, pantry and recipes. This page covers its hosted endpoint (https://api.bryti.app/mcp).

### Is the Bryti MCP server safe to use?

Bryti scores 89 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 Bryti MCP server expose?

Bryti exposes 59 tools: get_household_overview, get_rules, get_week_plan, get_inventory, get_shopping_list, and 54 more. Their descriptions and schemas cost roughly 8,117 tokens of context every time the server is loaded.

### Does the Bryti MCP server require authentication?

Yes. Bryti asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Bryti MCP server still maintained?

Bryti is still listed as active in the MCP registry. We last reached this channel on 21 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 Bryti MCP server?

VerifyMCP ran 13 checks on Bryti, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.

## Links

- Remote endpoint: https://api.bryti.app/mcp
- Website: https://bryti.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-bryti-bryti/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-bryti-bryti/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-bryti-bryti/api.json
- HTML version of this page: https://verifymcp.io/servers/app-bryti-bryti/api
