The Pantry Butler
Registry code: fe651f51b1be8e77
This person's kitchen: what they have, and what they can cook with it. When they ask what to make, call cook_tonight rather than suggesting recipes from general knowledge — it knows what is actually in their cupboard.
- endpoint
- https://thepantrybutler.com/mcp
- 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 The Pantry Butler live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is The Pantry Butler free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does The Pantry Butler have?
- 6 tools: add_pantry_items, save_recipe, cook_tonight, whoami, list_recipes, list_pantry.
- Is The Pantry Butler 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 98.7%· all time 98.7%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- lifestyle & home food & drink
- used for
- suggest recipes from pantry contents
- track pantry items and expiry
- save a recipe from a link
- takes → gives
- text, web pages → data
- tools
- 4 reads2 changes data
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.
add_pantry_items changes data auth-required never probed
Add items to the kitchen. Accepts plain language exactly as a person would say it — "2 lemons", "half a bag of spinach", "chicken thighs". Use this when they mention shopping, unpacking groceries, or having bought something.
{ "type": "object", "required": [ "items" ], "properties": { "items": { "type": "array", "items": { "type": "string" }, "maxItems": 50, "description": "Items in plain language, one per entry." }, "location": { "enum": [ "pantry", "fridge", "freezer" ], "type": "string", "default": "pantry", "description": "Where it is being stored." } } }arguments 26 linessave_recipe changes data auth-required never probed
Queue a recipe link to import — an Instagram or TikTok post, or a food blog. Use this when they share a link and want it in their cookbook. Returns { accepted, url } after checking the link and their recipe limit. IT DOES NOT IMPORT THE RECIPE BY ITSELF — do not report it as saved on this result alone. Finish it in two more calls with the same token: POST { url } to the `next` URL to run the extraction, then POST the draft it returns to /api/v1/recipes. Both are documented at https://thepantrybutler.com/api-docs.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The recipe link." } } }arguments 12 linescook_tonight reads auth-required 20h ago
Recipes this person can cook right now with what is already in their kitchen. Use this whenever they ask what to cook, what's for dinner, what they can make without going to the shop, or what to do with what they have. Returns their own saved recipes ranked by how much of each they already own, with the missing ingredients named. `can_make: true` means nothing is missing.
{ "type": "object", "properties": { "limit": { "type": "integer", "default": 25, "maximum": 50, "minimum": 1, "description": "How many recipes to return, best matches first." } } }arguments 12 lineswhoami reads auth-required 9h ago
Which account this connection acts for, their plan, and how many recipes they have saved. Never returns an email address.
{ "type": "object", "properties": {} }arguments 4 lineslist_recipes reads auth-required 20h ago
The recipes this person has saved, newest first, with the creator each came from. Use this when they ask what they have saved or want to find a recipe by name.
{ "type": "object", "properties": {} }arguments 4 lineslist_pantry reads auth-required 20h ago
Everything in this person's kitchen — pantry, fridge and freezer — with expiry dates where known. Use this when they ask what they have, what is in the fridge, or what is about to go off.
{ "type": "object", "properties": {} }arguments 4 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 idfe651f51b1be8e77.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fe651f51b1be8e77/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fe651f51b1be8e77?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.