# Foodbe (remote · foodbe-v3-production.up.railway.app)

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

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `foodbe-v3-production.up.railway.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/bleemohr-foodbe/v1-mcp.md), [page](https://verifymcp.io/servers/bleemohr-foodbe/v1-mcp)

## Channel facts

- Endpoint: `https://foodbe-v3-production.up.railway.app/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.1.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-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Foodbe MCP server?

Foodbe is a hosted endpoint at https://foodbe-v3-production.up.railway.app/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.

### Claude

```bash
claude mcp add --transport http bleemohr-foodbe 'https://foodbe-v3-production.up.railway.app/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "bleemohr-foodbe": {
      "url": "https://foodbe-v3-production.up.railway.app/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bleemohr-foodbe": {
      "type": "http",
      "url": "https://foodbe-v3-production.up.railway.app/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.bleemohr-foodbe]
url = "https://foodbe-v3-production.up.railway.app/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bleemohr-foodbe": {
      "type": "remote",
      "url": "https://foodbe-v3-production.up.railway.app/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bleemohr-foodbe --url 'https://foodbe-v3-production.up.railway.app/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bleemohr-foodbe:
    url: "https://foodbe-v3-production.up.railway.app/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "bleemohr-foodbe": {
      "Transport": "http",
      "Url": "https://foodbe-v3-production.up.railway.app/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add bleemohr-foodbe -t streamable-http -u 'https://foodbe-v3-production.up.railway.app/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "bleemohr-foodbe": {
      "type": "http",
      "url": "https://foodbe-v3-production.up.railway.app/v1/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-04 (score 71, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-03 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 70)

First indexed and scored.

## MCP tools (8)

### `foodbe_query` (~257 tokens)

The most complete read an agent can get on a food list. Call this before you plan, comment on, substitute or improve a grocery list, cart, order, menu or recipe, and before a human approves one. Send up to 50 ingredient names. Returns one fact-based, human-approved read of the whole cart: the health labels it carries, the total carbon and water, the balance across food groups with what to add, the flavor and texture it carries with the gap in each, and the diets it suits. It also returns swaps that keep flavor and texture. It returns a cook's read in chefy_read, broken down by food. Each food comes back with its own lines: how to cook it, what to use if you run out, and what it pairs with. A closing note names the cart's biggest gap and its carbon and water. Every line comes from Foodbe's stored data, never from a model, so the same cart always returns the same answer. Names Foodbe does not have are listed under not_found. A limited number of calls work without a key. After that, a key is needed in the x-foodbe-key header.

Input parameters:

- `question` (string, required): The food question to ask.

### `foodbe_query_all` (~152 tokens)

Looks up one food question in Foodbe's library of human-approved answers. Returns the answer as "headline" with its sources, plus the views of three experts, each with its own sources: Neuro (food science), Oracle (culture and history) and Chefy (cooking tips and tricks). 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. A limited number of calls work without a key. After that, a key is needed in the x-foodbe-key header.

Input parameters:

- `question` (string, required): The food question to ask.

### `foodbe_ingredient` (~85 tokens)

Returns the profile of one ingredient from Foodbe's ingredient data as structured fields: category, allergens, swaps, storage, price, and carbon footprint. Nutrition numbers are not included. A limited number of calls work without a key. After that, a key is needed in the x-foodbe-key header.

Input parameters:

- `name` (string, required): The ingredient name, for example apple.

### `foodbe_cart_breakdown` (~217 tokens)

Call this before you plan, comment on or improve a grocery list or food purchase. Send up to 50 ingredient names. Returns one fact-based, human-approved read of the whole cart: the health labels it carries, the total carbon and water, the balance across food groups with what to add, and the diets it suits. It also returns a cook's read in chefy_read, broken down by food. Each food comes back with its own lines: how to cook it, what to use if you run out, and what it pairs with. A closing note names the cart's biggest gap and its carbon and water. Every line comes from Foodbe's stored data, never from a model, so the same cart always returns the same answer. Names Foodbe does not have are listed under not_found. A limited number of calls work without a key. After that, a key is needed in the x-foodbe-key header.

Input parameters:

- `items` (array, required): The ingredient names in the cart, up to 50.

### `foodbe_recipe_finder` (~186 tokens)

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" and costs nothing. A limited number of calls work without a key. After that, a key is needed in the x-foodbe-key header.

Input parameters:

- `allergies` (array): Optional allergens to leave out, for example Peanuts.
- `diet` (string): Optional diet to filter by, for example Vegan.
- `dish` (string, required): The dish to find a recipe for, for example lasagna.

### `foodbe_meal_plan` (~238 tokens)

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" and costs nothing. A limited number of calls work without a key. After that, a key is needed in the x-foodbe-key header.

Input parameters:

- `allergies` (array): Optional allergens to leave out, for example Peanuts.
- `budget` (number): Optional most the whole plan may cost, in US dollars.
- `days` (integer): Optional number of days, from 1 to 7.
- `diet` (string): Optional diet to filter by, for example Vegan.

### `foodbe_grocery_list` (~219 tokens)

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" and costs nothing. A limited number of calls work without a key. After that, a key is needed in the x-foodbe-key header.

Input parameters:

- `allergies` (array): Optional allergens to leave out, for example Peanuts.
- `budget` (number): Optional most the whole plan may cost, in US dollars.
- `days` (integer): Optional number of days, from 1 to 7.
- `diet` (string): Optional diet to filter by, for example Vegan.
- `dish` (string): The dish to list the groceries for. Leave out when sending days or budget.

### `foodbe_feedback` (~117 tokens)

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. Free: no tokens are charged. Returns outcome "received". The number of messages per day is limited.

Input parameters:

- `kind` (string): Optional: missing_tool, wrong_answer or other.
- `message` (string, required): What is missing or wrong, 1 to 1000 characters.
- `tool` (string): Optional: the Foodbe tool name the feedback is about.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/bleemohr-foodbe/v1-mcp#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70

## 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://foodbe-v3-production.up.railway.app/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 8 tools: foodbe_query, foodbe_query_all, foodbe_ingredient, foodbe_cart_breakdown, foodbe_recipe_finder, and 3 more. Their descriptions and schemas cost roughly 1,471 tokens of context every time the server is loaded.

### Does the Foodbe MCP server require authentication?

Its publisher declares no required credentials for Foodbe. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Foodbe MCP server still maintained?

Foodbe is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 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 3 checks on Foodbe, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Foodbe: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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://foodbe-v3-production.up.railway.app/v1/mcp
- Website: https://www.foodbe.ai/
- Changelog RSS feed: https://verifymcp.io/servers/bleemohr-foodbe/v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/bleemohr-foodbe/v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/bleemohr-foodbe/v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/bleemohr-foodbe/v1-mcp