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.

ChefSums

REMOTE · CHEFSUMS.COM

Read-only UK kitchen costing: cost recipes, set menu prices, work out GP with VAT, build prep lists.

Available components

+3 this week 75 Trust /100

Last scanned (22 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 978 tokens (~163/item across 6 items; 6 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 Management30
  • Stability observed for 9 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (13)

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

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.

  • 21 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.

  • 19 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.

  • 17 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.

  • 14 Nov 26 +1

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

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 71

    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://chefsums.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=chefsums.com CN=YE1,O=Let's Encrypt,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA384 5df797a4daf7031878a926c2f41aa64358f
SANs: chefsums.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of chefsums.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
chefsums.com. 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
Header Value
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://chefsums.com/mcp Verified 200
http (plaintext) http://chefsums.com/mcp HTTPS enforced 308 https://chefsums.com/mcp
MCP tools · 6 exposed · ~855 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
build_prep_list ~114

Build a kitchen prep list from par levels: for each item give the par (the amount you want ready for service) and the amount on hand; prep quantity = par minus on hand, never below zero. Groups items by station.

NameTypeReqDescription
itemsarrayyesItems to prep, 1 to 200. Each needs a name, a par level and the amount on hand in the same unit; unit and station are optional.
titlestring–Optional title, e.g. 'Friday larder'.
NameTypeReqDescription
by_stationarrayyes–
free_template_urlstringyes–
itemsarrayyes–
items_already_at_parnumberyes–
items_to_prepnumberyes–
items_totalnumberyes–
titlestringyes–

No examples provided.

calculate_gp ~174

UK gross profit (GP) calculator for food and drink. mode 'gp_from_price': give cost_ex_vat and selling_price_inc_vat to get GP % and GP per sale (VAT is removed first, as UK hospitality measures it). mode 'price_from_gp': give cost_ex_vat and target_gp_pct to get the menu price needed.

NameTypeReqDescription
cost_ex_vatnumberyesCost of one item/portion, ex-VAT.
modestringyesgp_from_price or price_from_gp.
selling_price_inc_vatnumber–Menu price inc VAT. Required for gp_from_price.
target_gp_pctnumber–Target GP %. Required for price_from_gp.
vat_rate_pctnumber–VAT rate. Default 20; use 0 for zero-rated items.
NameTypeReqDescription
cost_ex_vatnumberyes–
food_cost_pctnumberyes–
gp_pctnumberyes–
gross_profitnumberyes–
modestringyes–
more_infostringyes–
net_price_ex_vatnumberyes–
selling_price_inc_vatnumberyes–
vat_rate_pctnumberyes–
verdictstringyes–

No examples provided.

cost_recipe ~249

Cost any recipe from its ingredients. For each ingredient give the pack price, the pack size and the quantity used (same unit as the pack size, e.g. grams). Returns each line cost, batch cost, cost per portion and a suggested menu price from a target food cost % (default 30%), ex-VAT and inc-VAT. open_in_prepsheet_url opens this exact recipe in the free ChefSums tool (no sign-in), where the user can edit, scale, print and save it; the recipe travels in the link itself and is not stored by ChefSums.

NameTypeReqDescription
ingredientsarrayyesThe recipe's ingredients, 1 to 100 lines. Each line needs a name, the ex-VAT pack price, the pack size and the quantity used in the same unit as the pack size.
portionsintegeryesHow many portions the batch makes.
recipe_namestring–Optional dish name.
target_food_cost_pctnumber–Target food cost as % of the ex-VAT price. Default 30.
vat_rate_pctnumber–VAT rate for the inc-VAT price. Default 20 (UK standard).
NameTypeReqDescription
batch_costnumberyes–
cost_per_portionnumberyes–
ingredientsarrayyes–
open_in_prepsheet_urlstringyes–
portionsnumberyes–
premium_price_ex_vat_at_75_gpnumber|nullyes–
premium_price_inc_vat_at_75_gpnumber|nullyes–
recipe_namestringyes–
suggested_price_ex_vatnumberyes–
suggested_price_inc_vatnumberyes–
target_food_cost_pctnumberyes–
target_gp_pctnumberyes–
vat_rate_pctnumberyes–

No examples provided.

get_recipe_prep_sheet ~123

Get a printable-style prep sheet for one ChefSums starter recipe, scaled to a number of covers (portions): every ingredient quantity scaled, the method, and the costing (batch cost, cost per portion, suggested menu price ex and inc 20% VAT). Example: slug 'cottage-pie', covers 80.

NameTypeReqDescription
coversinteger–Number of portions to scale to. Defaults to the recipe's base portions.
slugstringyesRecipe slug from list_starter_recipes, e.g. 'cottage-pie'.
NameTypeReqDescription
base_portionsnumberyes–
costingobjectyes–
coversnumberyes–
ingredientsarrayyes–
method_stepsarrayyes–
namestringyes–
notestringyes–
open_in_prepsheet_urlstringyes–
recipe_urlstringyes–
scale_factornumberyes–
slugstringyes–

No examples provided.

get_starter_menu ~107

Get ChefSums's ready-costed starter menu for a UK venue type. With no venue, lists the venue types (pub, cafe, restaurant, takeaway) and their dishes. With a venue, returns every dish with its menu price, ingredient cost per portion, food cost % and GP % (prices ex-VAT, plus inc 20% VAT).

NameTypeReqDescription
venuestring–One of pub, cafe, restaurant, takeaway. Omit to list the venue types.
NameTypeReqDescription
menu–yes–
more_infostringyes–
venuesarrayyes–

No examples provided.

list_starter_recipes ~88

List ChefSums's library of pre-costed UK starter recipes (pub, cafe, restaurant and takeaway dishes) with their base portions and ingredient cost per portion in GBP. Use the slug with get_recipe_prep_sheet. Optional 'search' filters by name (case-insensitive).

NameTypeReqDescription
searchstring–Optional text to filter recipe names, e.g. 'chicken'.
NameTypeReqDescription
countnumberyes–
more_infostringyes–
recipesarrayyes–

No examples provided.

Install

How do I install the ChefSums MCP server?

ChefSums is a hosted endpoint at https://chefsums.com/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 · chefsums.com

# add to Claude Code
claude mcp add --transport http com-chefsums-chefsums 'https://chefsums.com/mcp'
Common questions

What is the ChefSums MCP server?

ChefSums is an MCP server listed in the public MCP registry as com.chefsums/chefsums. Read-only UK kitchen costing: cost recipes, set menu prices, work out GP with VAT, build prep lists. This page covers its hosted endpoint (https://chefsums.com/mcp).

Is the ChefSums MCP server safe to use?

ChefSums scores 75 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 ChefSums MCP server expose?

ChefSums exposes 6 tools: list_starter_recipes, get_recipe_prep_sheet, get_starter_menu, cost_recipe, calculate_gp, build_prep_list. Their descriptions and schemas cost roughly 855 tokens of context every time the server is loaded.

Does the ChefSums MCP server require authentication?

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

Is the ChefSums MCP server still maintained?

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

VerifyMCP ran 13 checks on ChefSums, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.