whats-cooking
Registry code: 2c8b43b60582ddb5
Ask Gusto what to cook tonight from what someone has on hand (whats_for_dinner), or browse recipes people and Gusto have shared (browse_explore, get_explore_recipe). The full recipe comes back in the response — no need to send people anywhere.
- endpoint
- https://whatscooking.guide/mcp-server
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is whats-cooking live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is whats-cooking free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does whats-cooking have?
- 3 tools: get_explore_recipe, whats_for_dinner, browse_explore.
- Is whats-cooking safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
browse_explore open 1h ago
What recipes have people and Gusto shared on What's Cooking? Inputs (all optional): query (matched against titles, tags and ingredients), author (e.g. "Gusto"), limit (default 5, max 20). Returns short picks; call get_explore_recipe with an id for the full recipe. Example: {"query":"chicken","author":"Gusto"}
{ "type": "object", "properties": { "limit": { "type": "integer", "maximum": 20, "minimum": 1, "description": "How many picks. Default 5." }, "query": { "type": "string", "description": "A dish, ingredient or tag, e.g. \"chicken\" or \"vegan\"." }, "author": { "type": "string", "description": "Only recipes by this author, e.g. \"Gusto\"." } } }arguments 19 linesget_explore_recipe unknown 1h ago
What's the full recipe for this Explore pick? Inputs: id (from browse_explore, required), servings (optional; quantities are scaled when it differs from the original). Example: {"id":"<id from browse_explore>","servings":4}
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "The recipe id from browse_explore." }, "servings": { "type": "integer", "maximum": 48, "minimum": 1, "description": "Scale to this many servings." } } }arguments 18 lineswhats_for_dinner unknown never probed
What should I cook tonight with what I have? Gusto, What's Cooking's chef, decides one complete dinner and returns the full recipe, steps, and a list of what to buy. Inputs (all optional): have (what is already in the kitchen, a list or a sentence), cuisine, servings (default 2, max 24), diet (hard constraints such as vegetarian, vegan, gluten-free), max_minutes, mood, skill. Salt, pepper, oil and water are assumed on hand. Call again with different inputs for another idea. Example: {"have":["chicken"],"cuisine":"Mexican"}
{ "type": "object", "properties": { "diet": { "type": "array", "items": { "type": "string" }, "description": "Hard dietary constraints, e.g. [\"vegetarian\"]." }, "have": { "anyOf": [ { "type": "array", "items": { "type": "string" } }, { "type": "string" } ], "description": "Ingredients already on hand, e.g. [\"chicken\",\"rice\"] or \"chicken, rice and an onion\"." }, "mood": { "type": "string", "description": "e.g. cozy, light, celebratory." }, "skill": { "type": "string", "description": "e.g. beginner, confident." }, "cuisine": { "type": "string", "description": "e.g. Mexican, Thai, Italian." }, "servings": { "type": "integer", "maximum": 24, "minimum": 1, "description": "How many people. Default 2." }, "max_minutes": { "type": "integer", "minimum": 5, "description": "Total time limit in minutes." } } }arguments 49 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id2c8b43b60582ddb5.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2c8b43b60582ddb5/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2c8b43b60582ddb5?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.