RecipeScale
REMOTE · RECIPE-SCALE.MAGICTEAMS.AI
Scale recipes, convert kitchen units and merge shopping lists. Free.
Available components
Last scanned (12 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 23 Oct 2026.
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
- 18 Oct 26 +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.
- 16 Oct 26 +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.
- 14 Oct 26 +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.
- 12 Oct 26 +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.
- 10 Oct 26 0
- 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 security
- Schema quality: pass → fail ▼ functional
- “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” cosmetic
- 7 Oct 26 +3
- Stability: unverified → 0.10 ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
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 23 Oct 2026 · Probed https://recipe-scale.magicteams.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=magicteams.ai | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e30b351cd4e302030ea812aad87c2415 |
| SANs: magicteams.ai, recipe-scale.magicteams.ai, *.recipe-scale.magicteams.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of recipe-scale.magicteams.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| magicteams.ai. | absent | 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://recipe-scale.magicteams.ai/mcp | Verified | 200 | |
| http (plaintext) | http://recipe-scale.magicteams.ai/mcp | HTTPS enforced | 301 | https://recipe-scale.magicteams.ai/mcp |
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 →
convert_units Convert units ~245
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).
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | 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 | yes | Unit to convert to, e.g. 'g'; same supported units as from |
| value | number | yes | Amount to convert, zero or positive, e.g. 2 |
| Name | Type | Req | Description |
|---|---|---|---|
| density_note | string | – | Density used (density method only) |
| display | string | yes | Readable conversion, e.g. '2 cups flour = 250 g (approx.)' |
| from | string | yes | Canonical source unit, e.g. 'cup' |
| method | string | yes | 'linear' for same-dimension, 'density' for volume <-> weight |
| result | number | yes | Converted amount (4 significant digits) |
| to | string | yes | Canonical target unit, e.g. 'g' |
| value | number | yes | Amount that was converted |
No examples provided.
cost_per_serving Cost per serving ~143
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).
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency code for display only, e.g. 'EUR'; default USD |
| ingredients | array | yes | Priced ingredients, e.g. [{"item":"chicken","cost":8.5},{"item":"rice","cost":1.2}] |
| servings | number | yes | How many servings the recipe makes, positive, e.g. 4 |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | Currency code used in the results (upper case) |
| note | string | yes | Plain-language cost summary |
| per_serving | number | yes | Cost per serving, rounded to cents |
| per_ten_servings | number | yes | Cost for 10 servings, rounded to cents |
| servings | number | yes | Servings the recipe makes |
| total_cost | number | yes | Sum of all ingredient costs |
No examples provided.
merge_shopping_list Merge shopping list ~122
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).
| Name | Type | Req | Description |
|---|---|---|---|
| lists | array | yes | Shopping lists to merge (at least one item overall), e.g. [{"name":"Pancakes","items":[{"item":"milk","quantity":1,"unit":"cup"}]}] |
| Name | Type | Req | Description |
|---|---|---|---|
| merged | array | yes | One line per item and unit kind, with summed quantities |
| note | string | yes | Summary of the merge and its limits |
| skipped_no_quantity | array | yes | Items given without a quantity, kept as notes |
No examples provided.
scale_recipe Scale recipe ~174
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).
| Name | Type | Req | Description |
|---|---|---|---|
| from_servings | number | yes | Servings the recipe is written for, positive, e.g. 4 |
| ingredients | array | yes | Recipe ingredients, e.g. [{"item":"flour","quantity":2,"unit":"cup"},{"item":"salt","note":"to taste"}] |
| to_servings | number | yes | Servings wanted, positive; to_servings / from_servings must be 0.1-20, e.g. 10 |
| Name | Type | Req | Description |
|---|---|---|---|
| factor | number | yes | Scaling factor to_servings / from_servings (4 significant digits) |
| from_servings | number | yes | Servings the recipe was written for |
| ingredients | array | yes | Scaled ingredients, in input order |
| note | string | yes | Explanation of the scaling applied |
| to_servings | number | yes | Servings scaled to |
No examples provided.
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.
remote · recipe-scale.magicteams.ai
claude mcp add --transport http everyai-com-recipe-scale 'https://recipe-scale.magicteams.ai/mcp'
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.