# RecipeScale (remote · recipe-scale.magicteams.ai)

Scale recipes, convert kitchen units and merge shopping lists. Free.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `recipe-scale.magicteams.ai`: 78/100 (this document), [markdown](https://verifymcp.io/servers/everyai-com-recipe-scale/recipe-scale.md), [page](https://verifymcp.io/servers/everyai-com-recipe-scale/recipe-scale)

## Channel facts

- Endpoint: `https://recipe-scale.magicteams.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 732 tokens (~183/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge_shopping_list" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

RecipeScale is a hosted endpoint at https://recipe-scale.magicteams.ai/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 everyai-com-recipe-scale 'https://recipe-scale.magicteams.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "everyai-com-recipe-scale": {
      "url": "https://recipe-scale.magicteams.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "everyai-com-recipe-scale": {
      "type": "http",
      "url": "https://recipe-scale.magicteams.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.everyai-com-recipe-scale]
url = "https://recipe-scale.magicteams.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "everyai-com-recipe-scale": {
      "type": "remote",
      "url": "https://recipe-scale.magicteams.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add everyai-com-recipe-scale --url 'https://recipe-scale.magicteams.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  everyai-com-recipe-scale:
    url: "https://recipe-scale.magicteams.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "everyai-com-recipe-scale": {
      "Transport": "http",
      "Url": "https://recipe-scale.magicteams.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add everyai-com-recipe-scale -t streamable-http -u 'https://recipe-scale.magicteams.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "everyai-com-recipe-scale": {
      "type": "http",
      "url": "https://recipe-scale.magicteams.ai/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-10-23 (score 78, +1)

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

### 2026-10-21 (score 77, +1)

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

### 2026-10-18 (score 76, +1)

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

### 2026-10-16 (score 75, +1)

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

### 2026-10-14 (score 74, +1)

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

### 2026-10-12 (score 73, +1)

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

### 2026-10-10 (score 72, 0)

- [security] Tool “convert_units” rewrote its description, which is the text the model reads
- [security] Tool “cost_per_serving” rewrote its description, which is the text the model reads
- [security] Tool “merge_shopping_list” rewrote its description, which is the text the model reads
- [security] Tool “scale_recipe” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [cosmetic] “convert_units” reworded the description of “from”
- [cosmetic] “convert_units” reworded the description of “ingredient”
- [cosmetic] “convert_units” reworded the description of “to”
- [cosmetic] “convert_units” reworded the description of “value”
- [cosmetic] “cost_per_serving” reworded the description of “currency”
- [cosmetic] “cost_per_serving” reworded the description of “ingredients”
- [cosmetic] “cost_per_serving” reworded the description of “servings”
- [cosmetic] “merge_shopping_list” reworded the description of “lists”
- [cosmetic] “scale_recipe” reworded the description of “from_servings”
- [cosmetic] “scale_recipe” reworded the description of “ingredients”
- [cosmetic] “scale_recipe” reworded the description of “to_servings”

### 2026-10-07 (score 72, +3)

- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: good → excellent

## MCP tools (4)

### `scale_recipe` (~174 tokens)

Scale recipe

Scale every ingredient in a recipe from one serving count to another (0.1x to 20x), with kitchen-friendly fraction hints; items without a quantity pass through unchanged. Use when cooking for more or fewer people. Do NOT use to change units (use convert_units) or to combine several recipes' ingredients (use merge_shopping_list).

Input parameters:

- `from_servings` (number, required): Servings the recipe is written for, positive, e.g. 4
- `ingredients` (array, required): Recipe ingredients, e.g. [{"item":"flour","quantity":2,"unit":"cup"},{"item":"salt","note":"to taste"}]
- `to_servings` (number, required): Servings wanted, positive; to_servings / from_servings must be 0.1-20, e.g. 10

Output parameters:

- `factor` (number): Scaling factor to_servings / from_servings (4 significant digits)
- `from_servings` (number): Servings the recipe was written for
- `ingredients` (array): Scaled ingredients, in input order
- `note` (string): Explanation of the scaling applied
- `to_servings` (number): Servings scaled to

### `convert_units` (~245 tokens)

Convert units

Convert one cooking amount between units: within volume or weight exactly, or between volume and weight using a built-in density for flour, sugar, brown sugar, butter, water, milk, rice, oats, cocoa or honey. Use for questions like 'how many grams is 2 cups of flour'. Do NOT use to change serving counts (use scale_recipe).

Input parameters:

- `from` (string, required): Unit to convert from, e.g. 'cup'. Supported: tsp, tbsp, cup, fl_oz, ml, l, pint, quart, gallon (volume); g, kg, oz, lb (weight); each (count). Common spellings like 'cups', 'grams', 'tablespoon' also…
- `ingredient` (string): Ingredient name, required only for volume <-> weight; must contain one of flour, sugar, brown sugar, butter, water, milk, rice, oats, cocoa, honey (e.g. 'all-purpose flour')
- `to` (string, required): Unit to convert to, e.g. 'g'; same supported units as from
- `value` (number, required): Amount to convert, zero or positive, e.g. 2

Output parameters:

- `density_note` (string): Density used (density method only)
- `display` (string): Readable conversion, e.g. '2 cups flour = 250 g (approx.)'
- `from` (string): Canonical source unit, e.g. 'cup'
- `method` (string): 'linear' for same-dimension, 'density' for volume <-> weight
- `result` (number): Converted amount (4 significant digits)
- `to` (string): Canonical target unit, e.g. 'g'
- `value` (number): Amount that was converted

### `merge_shopping_list` (~122 tokens)

Merge shopping list

Combine several shopping or ingredient lists into one, summing the same item across lists (volumes and weights converted to a friendly unit) and noting which list each came from. Use when shopping for several recipes or meals at once. Do NOT use to resize one recipe (use scale_recipe) or price it (use cost_per_serving).

Input parameters:

- `lists` (array, required): Shopping lists to merge (at least one item overall), e.g. [{"name":"Pancakes","items":[{"item":"milk","quantity":1,"unit":"cup"}]}]

Output parameters:

- `merged` (array): One line per item and unit kind, with summed quantities
- `note` (string): Summary of the merge and its limits
- `skipped_no_quantity` (array): Items given without a quantity, kept as notes

### `cost_per_serving` (~143 tokens)

Cost per serving

Total the cost of a recipe's ingredients and work out the cost per serving and per 10 servings. Use when budgeting a dish, pricing meal prep or comparing recipes on cost. Do NOT use to resize the recipe (use scale_recipe first, then price the scaled amounts here).

Input parameters:

- `currency` (string): Currency code for display only, e.g. 'EUR'; default USD
- `ingredients` (array, required): Priced ingredients, e.g. [{"item":"chicken","cost":8.5},{"item":"rice","cost":1.2}]
- `servings` (number, required): How many servings the recipe makes, positive, e.g. 4

Output parameters:

- `currency` (string): Currency code used in the results (upper case)
- `note` (string): Plain-language cost summary
- `per_serving` (number): Cost per serving, rounded to cents
- `per_ten_servings` (number): Cost for 10 servings, rounded to cents
- `servings` (number): Servings the recipe makes
- `total_cost` (number): Sum of all ingredient costs

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/everyai-com-recipe-scale/recipe-scale#diagnostics

## Score history

- 2026-10-23: 78
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 76
- 2026-10-17: 75
- 2026-10-16: 75
- 2026-10-15: 74
- 2026-10-14: 74
- 2026-10-13: 73
- 2026-10-12: 73
- 2026-10-10: 72
- 2026-10-07: 72
- 2026-10-04: 69

## Common questions

### What is the RecipeScale MCP server?

RecipeScale is an MCP server listed in the public MCP registry as io.github.everyai-com/recipe-scale. Scale recipes, convert kitchen units and merge shopping lists. Free. This page covers its hosted endpoint (https://recipe-scale.magicteams.ai/mcp).

### Is the RecipeScale MCP server safe to use?

RecipeScale scores 78 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 RecipeScale MCP server expose?

RecipeScale exposes 4 tools: scale_recipe, convert_units, merge_shopping_list, cost_per_serving. Their descriptions and schemas cost roughly 684 tokens of context every time the server is loaded.

### Does the RecipeScale MCP server require authentication?

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

### Is the RecipeScale MCP server still maintained?

RecipeScale is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://recipe-scale.magicteams.ai/mcp
- Repository: https://github.com/everyai-com/sahadeva
- Changelog RSS feed: https://verifymcp.io/servers/everyai-com-recipe-scale/recipe-scale.xml
- Changelog JSON feed: https://verifymcp.io/servers/everyai-com-recipe-scale/recipe-scale.json
- HTML version of this page: https://verifymcp.io/servers/everyai-com-recipe-scale/recipe-scale