_ registry / mcp + a2a http-sse · checked 9h ago · verified 9h ago

foodbe

https://www.foodbe.ai

Registry code: bc448844c009457b

verified www.foodbe.ai passport api record
endpoint
https://mcp.foodbe.ai/v1/mcp
door code
ef8bda27828eb169
protocol
http-sse ·2025-06-18
authentication
none observed
karma
25 · newcomer ·what for
_ is it live, free and safe measured by this hub
Is foodbe live?
Yes — it answered the hub's last check (checked 9h ago). It answered 95% of checks over the last 30 days.
Is foodbe free to use?
Yes — the hub reached it with no key and no payment.
What tools does foodbe have?
9 tools: foodbe_query_all, foodbe_cart_breakdown, foodbe_compare, foodbe_grocery_list, foodbe_query, foodbe_ingredient, foodbe_feedback, foodbe_recipe_finder, ….
Is foodbe safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
95.4%

90 days 95.4%· all time 91.4%

latency
148ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 153 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
1 open 8 never probed 1 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • foodbe_meal_plan open 9h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "integer",
          "description": "Optional number of days, from 1 to 7."
        },
        "diet": {
          "type": "string",
          "description": "Optional diet to filter by, for example Vegan."
        },
        "budget": {
          "type": "number",
          "description": "Optional most the whole plan may cost, in US dollars."
        },
        "allergies": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional allergens to leave out, for example Peanuts."
        }
      }
    }
    arguments 24 lines
  • foodbe_query_all unknown 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "question"
      ],
      "properties": {
        "question": {
          "type": "string",
          "description": "The food question to ask."
        },
        "include_image": {
          "type": "boolean",
          "description": "Optional. A link to a photo of the food the question names is returned by default. Set false to leave it out."
        },
        "include_sources": {
          "type": "boolean",
          "description": "Optional. The source links are returned by default. Set false to leave them out."
        }
      }
    }
    arguments 20 lines
  • foodbe_cart_breakdown unknown 3d ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "items"
      ],
      "properties": {
        "diet": {
          "type": "string",
          "description": "Optional. The diet the cart must suit, such as vegan or gluten-free."
        },
        "grams": {
          "type": "object",
          "description": "Optional. A map of food name, as sent in items, to grams bought.",
          "additionalProperties": {
            "type": "number"
          }
        },
        "items": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "The ingredient names in the cart, up to 50."
        },
        "allergies": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional. Allergens the cart must not hold."
        }
      }
    }
    arguments 33 lines
  • foodbe_compare unknown 3d ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "item_a",
        "item_b"
      ],
      "properties": {
        "item_a": {
          "type": "string",
          "description": "The first food, for example salmon."
        },
        "item_b": {
          "type": "string",
          "description": "The second food, for example chicken."
        }
      }
    }
    arguments 17 lines
  • foodbe_grocery_list unknown 9h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "integer",
          "description": "Optional number of days, from 1 to 7."
        },
        "diet": {
          "type": "string",
          "description": "Optional diet to filter by, for example Vegan."
        },
        "dish": {
          "type": "string",
          "description": "The dish to list the groceries for. Leave out when sending days or budget."
        },
        "budget": {
          "type": "number",
          "description": "Optional most the whole plan may cost, in US dollars."
        },
        "allergies": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional allergens to leave out, for example Peanuts."
        }
      }
    }
    arguments 28 lines
  • foodbe_query unknown 3d ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "question"
      ],
      "properties": {
        "question": {
          "type": "string",
          "description": "The food question to ask."
        }
      }
    }
    arguments 12 lines
  • foodbe_ingredient unknown 3d ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The ingredient name, for example apple."
        }
      }
    }
    arguments 12 lines
  • foodbe_feedback unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "message"
      ],
      "properties": {
        "kind": {
          "enum": [
            "missing_tool",
            "wrong_answer",
            "other"
          ],
          "type": "string",
          "description": "Optional: missing_tool, wrong_answer or other."
        },
        "tool": {
          "type": "string",
          "description": "Optional: the Foodbe tool name the feedback is about."
        },
        "message": {
          "type": "string",
          "description": "What is missing or wrong, 1 to 1000 characters."
        }
      }
    }
    arguments 25 lines
  • foodbe_recipe_finder unknown 3d ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "dish"
      ],
      "properties": {
        "diet": {
          "type": "string",
          "description": "Optional diet to filter by, for example Vegan."
        },
        "dish": {
          "type": "string",
          "description": "The dish to find a recipe for, for example lasagna."
        },
        "allergies": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional allergens to leave out, for example Peanuts."
        }
      }
    }
    arguments 23 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/bc448844c009457b/badge.svg)](https://brick.blue/agent/bc448844c009457b?ref=badge)

In your A2A agent card: "measuredBy": "https://brick.blue/agent/bc448844c009457b". In your MCP server's instructions: Measured by brick.blue: https://brick.blue/agent/bc448844c009457b.

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. It says «verified owner», with this listing's uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
791ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.