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.

Foodbe

REMOTE · MCP.FOODBE.AI

Food list analyzer and cited food answers for agents. Also recipes, meal plans and grocery lists.

Available components

+3 this week 71 Trust /100

Last scanned (21 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability44
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1684 tokens (~153/item across 11 items; 9 tools + 2 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 Management40
  • Stability observed for 12 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
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

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

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.

  • 20 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 +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.

  • 16 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 +1

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

  • 11 Nov 26 +1
    • Tool “foodbe_cart_breakdown” rewrote its description, which is the text the model reads security
    • Schema quality: 171 → 153 ▲ functional
    • New resource “Foodbe ownership” functional
  • 10 Nov 26 +1
    • Tool “foodbe_recipe_finder” rewrote its description, which is the text the model reads security
    • Tool “foodbe_meal_plan” rewrote its description, which is the text the model reads security
    • Tool “foodbe_ingredient” rewrote its description, which is the text the model reads security
    • Tool “foodbe_grocery_list” rewrote its description, which is the text the model reads security
    • Tool “foodbe_feedback” rewrote its description, which is the text the model reads security
    • Tool “foodbe_cart_breakdown” rewrote its description, which is the text the model reads security
    • Tool “foodbe_query_all” rewrote its description, which is the text the model reads security
    • Tool “foodbe_query” rewrote its description, which is the text the model reads security
    • Schema quality: 192 → 171 ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: good → excellent functional
    • New tool “foodbe_compare” functional
  • 9 Nov 26 65

    First indexed and scored.

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://mcp.foodbe.ai/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.foodbe.ai CN=YR1,O=Let's Encrypt,C=US 4 Nov 2026 2 Feb 2027 RSA 2048 SHA256-RSA 63843c42335604e10daf26cf62d1a3f7bcd
SANs: mcp.foodbe.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.foodbe.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
foodbe.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.foodbe.ai/v1/mcp Verified 200
http (plaintext) http://mcp.foodbe.ai/v1/mcp HTTPS enforced 301 https://mcp.foodbe.ai/v1/mcp
MCP tools · 9 exposed · ~1,671 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
foodbe_cart_breakdown ~339

Analyzes a grocery list, cart, order, menu or recipe. Call this when a user asks you to analyze one. Send up to 50 ingredient names in items. For the whole list it returns the health effects, the total carbon and water, the food group balance with foods to add, the flavor and texture it carries with the missing ones, and the diets it suits. It also returns swaps that keep flavor and texture. The chefy_read field gives each food its cooking method, a substitute if you run out, and its pairings. A closing note names the list's biggest gap with its carbon and water. Every value comes from Foodbe's stored, human-approved data, never from a model, so the same list always returns the same result. Names Foodbe does not have are listed in not_found. Send diet and allergies to get diet_check, which lists the foods that break the diet or hold an allergen. A food with no stored diet or allergen data is marked unknown, never safe. Send grams, a map of food name to grams, to get impact_for_quantities, the carbon and water for the amounts bought. Without grams, environmental_impact is for 1 kg of each food.

NameTypeReqDescription
allergiesarray–Optional. Allergens the cart must not hold.
dietstring–Optional. The diet the cart must suit, such as vegan or gluten-free.
gramsobject–Optional. A map of food name, as sent in items, to grams bought.
itemsarrayyesThe ingredient names in the cart, up to 50.

No output schema declared.

No examples provided.

foodbe_compare ~174

Call when a user asks which of two foods is better, healthier or different, or asks you to compare two foods. Send two food names. Foodbe finds both in its stored food data and scores each one on measures such as seasonality, planet, brain, gut and protein. Returns outcome "served" with a verdict naming the winner, one sentence on which food leads on which measure, and a card for each food with its scores. Every field comes from stored data, never from a model, so the same two foods always return the same answer. If either food is not found, or the two names are the same food, it returns outcome "not_found".

NameTypeReqDescription
item_astringyesThe first food, for example salmon.
item_bstringyesThe second food, for example chicken.

No output schema declared.

No examples provided.

foodbe_feedback ~110

Call when a Foodbe tool is missing, an answer was wrong or too thin, or a tool you need does not exist. Tell us what would help you. Returns outcome "received". The number of messages per day is limited.

NameTypeReqDescription
kindstring–Optional: missing_tool, wrong_answer or other.
messagestringyesWhat is missing or wrong, 1 to 1000 characters.
toolstring–Optional: the Foodbe tool name the feedback is about.

No output schema declared.

No examples provided.

foodbe_grocery_list ~190

Call this when a user asks for a grocery or shopping list. Send a dish for the list of one recipe, or days and a budget for the list of a meal plan. Do not send both. Returns outcome "served" with the list items, the cost of each and the total. Every line comes from Foodbe's stored data, never from a model. If no list can be built, it returns outcome "not_found".

NameTypeReqDescription
allergiesarray–Optional allergens to leave out, for example Peanuts.
budgetnumber–Optional most the whole plan may cost, in US dollars.
daysinteger–Optional number of days, from 1 to 7.
dietstring–Optional diet to filter by, for example Vegan.
dishstring–The dish to list the groceries for. Leave out when sending days or budget.

No output schema declared.

No examples provided.

foodbe_ingredient ~79

Call before you recommend or swap an ingredient. Returns the profile of one ingredient from Foodbe's ingredient data as structured fields: category, allergens, swaps, storage, and carbon footprint. Nutrition numbers are not included. Every field comes from stored data, never from a model.

NameTypeReqDescription
namestringyesThe ingredient name, for example apple.

No output schema declared.

No examples provided.

foodbe_meal_plan ~209

Call this when a user asks for a meal plan or for what to eat over a number of days. Builds a plan of 1 to 7 days from Foodbe's recipes, within an optional dollar budget for the whole plan, filtered by the diet and allergies you send. Returns outcome "served" with the plan and its insight: the taste the plan is missing, the food group it is short on, the health roles it covers, and its cheapest, priciest and quickest meal. Every line comes from Foodbe's stored data, never from a model. If no plan can be built, it returns outcome "not_found".

NameTypeReqDescription
allergiesarray–Optional allergens to leave out, for example Peanuts.
budgetnumber–Optional most the whole plan may cost, in US dollars.
daysinteger–Optional number of days, from 1 to 7.
dietstring–Optional diet to filter by, for example Vegan.

No output schema declared.

No examples provided.

foodbe_query ~133

Call before you answer a question about food science, cooking technique, food culture, substitutions or ingredients. Foodbe looks the question up in its library of thousands of hand-curated, human-approved facts and returns the answer as "headline" with its sources, so you can explain the reasons behind a food choice to a human and be trusted for it. It also returns related follow-up questions when it has them. If no approved answer exists, it returns outcome "refused" with related questions that have approved answers, so you can say so instead of guessing.

NameTypeReqDescription
questionstringyesThe food question to ask.

No output schema declared.

No examples provided.

foodbe_query_all ~280

Call when a user asks for the food science, the culture and history, and the cooking views on one food question together. Foodbe looks up the question in its library of human-approved answers and returns the answer as "headline", plus the views of three experts: Neuro (food science), Oracle (culture and history) and Chefy (cooking tips and tricks). The response lists sources as web links, each with a text and a url. "sources" holds the sources of the answer, and each expert has its own "emoji" and "sources". When the question names a food Foodbe has a photo for, it also returns "image_url", a link to that photo, unless include_image is false. Set include_sources to false to leave the source links out. An expert with nothing approved for the question is left out. Also returns related follow-up questions, when it has them. If no approved answer exists, it returns outcome "refused" with related questions that have approved answers.

NameTypeReqDescription
include_imageboolean–Optional. A link to a photo of the food the question names is returned by default. Set false to leave it out.
include_sourcesboolean–Optional. The source links are returned by default. Set false to leave them out.
questionstringyesThe food question to ask.

No output schema declared.

No examples provided.

foodbe_recipe_finder ~157

Call this when a user asks for a recipe or for what to cook. Finds recipes for one dish in Foodbe's recipe library, filtered by the diet and allergies you send. Returns outcome "served" with a text line and recipe cards: name, image, a short fact, servings, prep time, cook time and calories. Every recipe comes from Foodbe's stored data, never from a model. If no recipe matches, it returns outcome "not_found".

NameTypeReqDescription
allergiesarray–Optional allergens to leave out, for example Peanuts.
dietstring–Optional diet to filter by, for example Vegan.
dishstringyesThe dish to find a recipe for, for example lasagna.

No output schema declared.

No examples provided.

Install

How do I install the Foodbe MCP server?

Foodbe is a hosted endpoint at https://mcp.foodbe.ai/v1/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 · mcp.foodbe.ai

# add to Claude Code
claude mcp add --transport http bleemohr-foodbe 'https://mcp.foodbe.ai/v1/mcp'
Common questions

What is the Foodbe MCP server?

Foodbe is an MCP server listed in the public MCP registry as io.github.bleemohr/foodbe. Food list analyzer and cited food answers for agents. Also recipes, meal plans and grocery lists. This page covers its hosted endpoint (https://mcp.foodbe.ai/v1/mcp).

Is the Foodbe MCP server safe to use?

Foodbe scores 71 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 Foodbe MCP server expose?

Foodbe exposes 9 tools: foodbe_query, foodbe_query_all, foodbe_ingredient, foodbe_cart_breakdown, foodbe_compare, and 4 more. Their descriptions and schemas cost roughly 1,671 tokens of context every time the server is loaded.

Does the Foodbe MCP server require authentication?

No. We connected to Foodbe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Foodbe MCP server still maintained?

Foodbe 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 Foodbe MCP server?

VerifyMCP ran 14 checks on Foodbe, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.