MCP servers observed by Lowdown
app.bryti/bryti MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 59 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 after 6 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.bryti/bryti
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.bryti/bryti?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 2 compared days.
- 2026-11-17: input or output schemas changed, descriptions changed
What tools does it list?
59 tools on 2026-11-17:
activate_planadapt_dinner_ingredientadd_food_preferenceadd_guests_for_dateadd_inventory_observationadd_shopping_itemcheck_shopping_itemclear_weekdelete_food_preferencedelete_meal_eventdelete_recipedelete_ruleedit_recipeget_calendar_eventsget_dayget_household_overviewget_inventoryget_meal_eventsget_planned_dinnerget_planning_statusget_recipeget_recipesget_rulesget_shopping_guideget_shopping_listget_storesget_week_planimport_recipe_from_urlmark_awaymark_eating_outmark_member_absentmerge_pantry_foodsplan_weekrecord_outcomeremove_shopping_itemreplace_dinnerreplan_open_dayssave_recipesearch_helpsearch_tipsselect_storesset_category_for_dateset_dinner_lockset_dinner_timeset_household_languageset_leftover_dinnersset_lunchbox_portionsset_max_cooking_time_for_dateset_prep_daysset_recipe_favoriteupdate_household_settingsupsert_category_excluded_days_ruleupsert_category_frequency_ruleupsert_category_on_day_ruleupsert_max_cooking_time_ruleupsert_max_total_time_ruleupsert_price_class_ruleupsert_repeat_after_days_rulewish_dish
MCP Registry declaration
- Registry name:
app.bryti/bryti - Declared version: 1.0.0
- Status: active
- Declared hosts:
api.bryti.app
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:app.bryti/bryti", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.bryti/bryti?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).