Chef
app.netlify.kitchen-passPublished by kitchen-pass.netlify.appv0.3.0Updated Nov 7, 2026
A head chef's verified answers as tools: scale recipes, fix cooking faults, swaps, yields and costs.
Overview
Local MCP server that gives an assistant a head chef's verified answers as tools for scaling recipes, fixing cooking faults, swaps, yields and costs.
- What you can do
- Scale recipes and adjust quantities for different serving sizes
- Diagnose and fix cooking faults
- Suggest ingredient swaps
- Work out yields and estimate costs
- Quote answers without paying when no wallet key file is configured
- When to use it
- Useful when you want an assistant to answer practical kitchen questions — resizing a recipe, rescuing a dish that went wrong, substituting an ingredient, or estimating yield and cost — with answers drawn from a chef rather than generated freely.
- Requirements
- Runs as a local npm package over stdio on a desktop machine. Requires the KITCHEN_PASS_NETWORK variable set to base (real USDC) or base-sepolia (test USDC). Optional KITCHEN_PASS_PAYER_KEY_FILE points to an absolute path of your own wallet key file with mode 600; without it the server only quotes. Optional KITCHEN_PASS_MAX_SPEND_PER_DAY (default 0.50 USD, max 20) and KITCHEN_PASS_MAX_SPEND_PER_SESSION (default 0.10 USD, max 5) cap spending.
Installation
In SourceWeft
- Open Chef in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
3- v0.3.0LatestNov 7, 2026
- v0.2.0Oct 21, 2026
- v0.1.0Oct 13, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.