Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bryti

REMOTE · API.BRYTI.APP

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

Available components

+4 this week 89 Trust /100

Last scanned (15 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

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 Security100
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. View diagnostics → Pass
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 8494 tokens (~143/item across 59 items; 59 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 60 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 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.

  • 18 Nov 26 0
    • “update_household_settings” added an optional parameter “saveGeneratedRecipes” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 14 Nov 26 0
    • 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 security
    • “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 cosmetic
  • 12 Nov 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.

  • 11 Nov 26 0
    • New tool “set_lunchbox_portions” functional
    • “update_household_settings” added an optional parameter “lunchboxWeekdayPortions” cosmetic
Diagnostics

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 21 Nov 2026 · Probed https://api.bryti.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bryti.app CN=YE2,O=Let's Encrypt,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA384 6fb60fa083019c4eaa4068519b038695194
SANs: *.bryti.app, bryti.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 secure

Validation of api.bryti.app. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
bryti.app. DS published 2371 13 Verified
api.bryti.app. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://api.bryti.app/.well-known/oauth-protected-resource/mcp", scope="household:read household:write", error_description="Sign in to Bryti to continue"

Bearer resource_metadata="https://api.bryti.app/.well-known/oauth-protected-resource/mcp", scope="household:read household:write", error_description="Sign in to Bryti to continue"
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()

Protected resource metadata

Document https://api.bryti.app/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://api.bryti.app/mcp
Authorisation server https://api.bryti.app

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.bryti.app/mcp Verified 200
http (plaintext) http://api.bryti.app/mcp HTTPS enforced 301 https://api.bryti.app/mcp
MCP tools · 59 exposed · ~8,117 tokens

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 →

Tool Tokens
activate_plan ~64

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.

NameTypeReqDescription
weekStartstringyesAny date in the week; resolved to that week's plan.

No output schema declared.

No examples provided.

adapt_dinner_ingredient ~127

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.

NameTypeReqDescription
datestringyesThe dinner date, ISO date.
insteadOfFoodstringyesThe ingredient in that dinner it replaces, e.g. «fløte» / «cream».
useFoodstringyesWhat to use — the food the household already has, e.g. «melk» / «milk».

No output schema declared.

No examples provided.

add_food_preference ~141

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.

NameTypeReqDescription
memberNamestring–Member the preference belongs to; omit for the whole household.
sentimentstringyesHow strongly they feel.
subjectstringyesThe food, ingredient, or dish. For subjectType Taste prefer the canonical lowercase English keys: sweet, salty, sour, bitter, umami, spicy, rich, fresh.
subjectTypestringyesWhat the subject refers to.

No output schema declared.

No examples provided.

add_guests_for_date ~185

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.

NameTypeReqDescription
adultCountintegeryesNumber of anonymous adult guests (not counting named ones).
babyCountinteger–Number of baby guests (under about two years): they eat from a parent's plate, but the dinner must be safe for them.
childCountintegeryesNumber of anonymous child guests (not counting named ones).
datestringyesThe dinner date (first day for a multi-day visit), ISO date.
endDatestring–Last day of a multi-day visit, ISO date; omit for a single dinner.
guestNamesarray–Usual guests coming by name.
notesstring–Optional note, e.g. 'grandparents'.

No output schema declared.

No examples provided.

add_inventory_observation ~129

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

NameTypeReqDescription
displayNamestringyesHuman-readable name, e.g. 'Salmon fillet'.
foodKeystring–Leave this out: Bryti finds the food from displayName.
observationTypestringyesWhat was observed.
quantitynumber–Amount, if known.
storageLocationstringyesWhere it is stored.
unitstring–Unit for the quantity, e.g. 'g', 'dl', 'pcs'.

No output schema declared.

No examples provided.

add_shopping_item ~131

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

NameTypeReqDescription
displayNamestringyesWhat to buy, e.g. 'melk' or 'kaffe'. Include the amount in quantity/unit rather than in the name.
quantitynumber–Amount, if the user said one, e.g. 2.
unitstring–Unit for the quantity, e.g. 'l', 'stk', 'g'; omit if none.
weekStartstringyesAny date in the week whose list gets the item.

No output schema declared.

No examples provided.

check_shopping_item ~90

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

NameTypeReqDescription
itemNamestringyesThe item's display name, e.g. 'melk'.
purchasedbooleanyestrue = bought it; false = back on the list.
weekStartstringyesAny date in the week whose list holds the item.

No output schema declared.

No examples provided.

clear_week ~127

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.

NameTypeReqDescription
includeLockedboolean–True only when the household has said the locked days go too.
weekStartstringyesAny date in the week; resolved to that week's plan.

No output schema declared.

No examples provided.

delete_food_preference ~70

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

NameTypeReqDescription
memberNamestring–Member it belongs to; omit for a household-level preference.
subjectstringyesThe recorded subject, e.g. 'broccoli' or 'spicy'.

No output schema declared.

No examples provided.

delete_meal_event ~83

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.

NameTypeReqDescription
datestringyesThe date whose events to remove, ISO date.
eventTypestring–Only remove events of this type; omit for all.

No output schema declared.

No examples provided.

delete_recipe ~58

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.

NameTypeReqDescription
titlestringyesExact title of the recipe to delete.

No output schema declared.

No examples provided.

delete_rule ~88

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.

NameTypeReqDescription
ruleIdstringyesThe rule's id, as get_rules shows it.

No output schema declared.

No examples provided.

edit_recipe ~377

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.

NameTypeReqDescription
activeMinutesinteger–Hands-on cooking minutes.
categorystring–The meal category.
equipmentarray–What the kitchen needs that is not food. Never on the shopping list. On edit_recipe the list replaces it.
ingredientsarray–The COMPLETE new ingredient list.
newTitlestring–A new title, when the dish is being renamed.
notestring–The recipe's own note: the intro and the author's assessment. On edit_recipe an empty string removes it.
ovenSettingsarray–The oven per step. On edit_recipe the list replaces all of them.
portionsinteger–How many portions the base quantities make.
recipeTitlestringyesThe recipe's current title.
stepNotesarray–Notes under the steps. On edit_recipe the list replaces all of them.
stepsarray–The COMPLETE new list of steps.
tagsarray–The complete new tag list.
timelinearray–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…
totalMinutesinteger–Total minutes from start to serving (≥ active).

No output schema declared.

No examples provided.

get_calendar_events ~68

Read the household's calendar events between two dates.

NameTypeReqDescription
fromstring–First day to read, ISO date (yyyy-MM-dd); defaults to today.
tostring–Last day to read, ISO date (yyyy-MM-dd); defaults to 14 days after 'from'.

No output schema declared.

No examples provided.

get_day ~68

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

NameTypeReqDescription
datestringyesThe day asked about, ISO date (yyyy-MM-dd) — resolve «tirsdag» to the nearest Tuesday from today, «i morgen» to tomorrow.

No output schema declared.

No examples provided.

get_household_overview ~36

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_inventory ~133

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

NameTypeReqDescription
cursorstring–The `nextCursor` of the page before; omit for the first page.
groupstring–Only this section: UseSoon (should be used up), LikelyAvailable, Uncertain (nobody has confirmed it), Aged (the archive).
limitinteger–Rows per page, 1-100; 40 when omitted.
placestring–Only this storage location.
querystring–A food to look for; omit for everything.

No output schema declared.

No examples provided.

get_meal_events ~121

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

NameTypeReqDescription
cursorstring–The `nextCursor` of the page before; omit for the first page.
fromstring–First day to read, ISO date; defaults to today.
limitinteger–Events per page, 1-100; 50 when omitted.
tostring–Last day to read, ISO date; defaults to 30 days after 'from'. At most 92 days after it.

No output schema declared.

No examples provided.

get_planned_dinner ~39

Read the planned dinner and its recipe for one date.

NameTypeReqDescription
datestringyesThe dinner date, ISO date (yyyy-MM-dd).

No output schema declared.

No examples provided.

get_planning_status ~84

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.

NameTypeReqDescription
jobIdstring–The jobId plan_week or replan_open_days answered with. Omit for the latest run.

No output schema declared.

No examples provided.

get_recipe ~37

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

NameTypeReqDescription
recipeIdstringyesId of the recipe, from get_recipes.

No output schema declared.

No examples provided.

get_recipes ~145

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

NameTypeReqDescription
categorystring–Only dinners of this category.
cursorstring–The `nextCursor` of the page before; omit for the first page.
favouritesboolean–Only the dishes the household has marked as favourites, its own and the starter library's.
limitinteger–Recipes per page, 1-100; 40 when omitted.
querystring–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.

No output schema declared.

No examples provided.

get_rules ~29

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_shopping_guide ~103

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.

NameTypeReqDescription
storestringyesThe 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…

No output schema declared.

No examples provided.

get_shopping_list ~89

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.

NameTypeReqDescription
weekStartstring–Monday of the week, ISO date (yyyy-MM-dd). Leave it out for the current week.

No output schema declared.

No examples provided.

get_stores ~17

Read the stores the household shops in.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_week_plan ~101

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

NameTypeReqDescription
cursorstring–The `nextCursor` of the page before — the date that page stopped at; omit for the first page.
limitinteger–Days per page, 1-31; the whole week when omitted.
weekStartstringyesMonday of the week, ISO date (yyyy-MM-dd).

No output schema declared.

No examples provided.

import_recipe_from_url ~73

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.

NameTypeReqDescription
urlstringyesThe recipe page's full https address.

No output schema declared.

No examples provided.

mark_away ~138

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.

NameTypeReqDescription
datestringyesFirst 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)'.
endDatestring–Last day away, ISO date; omit for a single day. Never earlier than 'date' — a span runs forwards from its first day.
notesstring–Optional note, e.g. 'cabin trip'.

No output schema declared.

No examples provided.

mark_eating_out ~91

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.

NameTypeReqDescription
datestringyesThe date (first day for a span), ISO date.
endDatestring–Last day of the span, ISO date; omit for a single evening.
notesstring–Optional note.

No output schema declared.

No examples provided.

mark_member_absent ~63

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

NameTypeReqDescription
datestringyesThe date, ISO date.
memberNamestringyesName of the member who is away.

No output schema declared.

No examples provided.

merge_pantry_foods ~121

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.

NameTypeReqDescription
fromFoodKeystringyesCanonical lowercase key of the row that stops being its own, e.g. 'fusilli'.
toFoodKeystringyesCanonical lowercase key of the row that survives and gives the merged row its name, e.g. 'pasta'.

No output schema declared.

No examples provided.

plan_week ~260

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.

NameTypeReqDescription
allowGenerationinteger–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.
allowNearMissesboolean–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…
replaceboolean–True when the member has said yes to replacing the dinners already planned this week.
weekStartstringyesAny date in the week to plan; normalized to that week's Monday.

No output schema declared.

No examples provided.

record_outcome ~91

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

NameTypeReqDescription
datestringyesThe dinner date, ISO date.
notesstring–Optional note from the user.
reasonstring–Why it wasn't cooked as planned; on a made dinner only DidNotLike, else omit.
statusstringyesWhat happened to the dinner.

No output schema declared.

No examples provided.

remove_shopping_item ~78

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.

NameTypeReqDescription
itemNamestringyesThe item's name as the list shows it, e.g. 'melk'.
weekStartstringyesAny date in the week whose list holds the item.

No output schema declared.

No examples provided.

replace_dinner ~112

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.

NameTypeReqDescription
datestringyesThe dinner date, ISO date.
dishTitlestringyesTitle of the dish to switch to: one of the day's suggestions, or a recipe in the library.

No output schema declared.

No examples provided.

replan_open_days ~77

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.

NameTypeReqDescription
weekStartstringyesAny date in the week; resolved to that week's plan.

No output schema declared.

No examples provided.

save_recipe ~418

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.

NameTypeReqDescription
activeMinutesintegeryesHands-on cooking minutes.
categorystringyesThe meal category.
equipmentarray–What the kitchen needs that is not food. Never on the shopping list. On edit_recipe the list replaces it.
ingredientsarrayyesThe ingredients with quantities.
languagestring–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.
notestring–The recipe's own note: the intro and the author's assessment. On edit_recipe an empty string removes it.
ovenSettingsarray–The oven per step. On edit_recipe the list replaces all of them.
portionsintegeryesHow many portions the base quantities make.
stepNotesarray–Notes under the steps. On edit_recipe the list replaces all of them.
stepsarrayyesOrdered cooking steps.
tagsarrayyesDescriptive tags; may be empty.
timelinearray–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…
titlestringyesRecipe title, e.g. 'Grandma's fish soup'.
totalMinutesintegeryesTotal minutes from start to serving (≥ active).

No output schema declared.

No examples provided.

search_help ~59

Search Bryti's help articles.

NameTypeReqDescription
languagestring–'nb' or 'en' — the language of the question; defaults to the household's.
querystringyesThe question, in the household's own words and language.

No output schema declared.

No examples provided.

search_tips ~67

Search Bryti's fact-checked kitchen tips.

NameTypeReqDescription
querystringyesThe 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»).

No output schema declared.

No examples provided.

select_stores ~128

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.

NameTypeReqDescription
addressstring–Address the stores are near; omit when they are near the household's own address.
storeAddressesarray–Only for an undo: the address each store was found near, in the same order as storeNames.
storeNamesarrayyesThe stores to shop at.

No output schema declared.

No examples provided.

set_category_for_date ~228

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.

NameTypeReqDescription
categorystringyesThe meal category for that day.
datestringyesThe date, ISO date.
strengthstringyesSoft 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…

No output schema declared.

No examples provided.

set_dinner_lock ~58

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

NameTypeReqDescription
datestringyesThe dinner date, ISO date.
lockedbooleanyestrue = pin the dinner; false = unpin.

No output schema declared.

No examples provided.

set_dinner_time ~88

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

NameTypeReqDescription
datestring–The evening to move, ISO date; omit for today.
timestringyesWhen dinner is served, 24-hour HH:mm.
weekdaysarray–Make it a standing rule for these weekdays; omit for this evening only.

No output schema declared.

No examples provided.

set_household_language ~90

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.

NameTypeReqDescription
languageCodestringyesBCP-47 code: 'nb' (bokmål), 'nn' (nynorsk) or 'en'.

No output schema declared.

No examples provided.

set_leftover_dinners ~53

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

NameTypeReqDescription
enabledbooleanyesTrue to plan leftover dinners, false for never.

No output schema declared.

No examples provided.

set_lunchbox_portions ~119

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.

NameTypeReqDescription
datestringyesThe dinner's date, yyyy-MM-dd.
portionsinteger–Extra portions for the next day's lunchboxes, 0–10. Leave it out to follow the household's weekday setting again.

No output schema declared.

No examples provided.

set_max_cooking_time_for_date ~225

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

NameTypeReqDescription
datestringyesThe date, ISO date.
minutesintegeryesMaximum active minutes at the stove.
strengthstringyesSoft 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…

No output schema declared.

No examples provided.

set_prep_days ~161

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.

NameTypeReqDescription
freezesPrepboolean–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.
timestring–When prep starts on those days, 24-hour HH:mm. Omit to keep the hour the household has (15:00 when it has none).
weekdaysarrayyesThe prep days. Empty turns prep days off.

No output schema declared.

No examples provided.

set_recipe_favorite ~97

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.

NameTypeReqDescription
favoritebooleanyestrue = mark as favorite; false = remove the mark.
memberNamestring–Member the favorite belongs to; omit for the whole family.
recipeTitlestringyesExact title of the recipe, from get_recipes.

No output schema declared.

No examples provided.

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.

remote · api.bryti.app

# add to Claude Code
claude mcp add --transport http app-bryti-bryti 'https://api.bryti.app/mcp'
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.