Kitchen Timer
Plan a meal and run kitchen timers that ring on your phone. No sign-in.
| Endpoint | https://kt.tnyforge.com/mcp/open (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 9 tools · grade C (66) · pin ts_77ae4315b6cbca6231d9b30301fe544a · protocol 2025-06-18 |
| First / last listed | 2026-11-08 02:58 UTC / 2026-11-08 02:58 UTC |
| Grade over time | 2026-11-08: C (66), 9 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: plan_meal meal_status pause_meal resume_meal adjust_dish skip_step add_dish link_dish cancel_meal
plan_meal | Make a meal plan: each dish starts at the right moment so everything is ready at the same time. Returns a link (open it on the phone in the kitchen, where the alarms ring), a QR code for that link, and the schedule. YOU do the cooking knowledge: break a recipe into dishes, each with its total cooking minutes, and put the timed moments inside a dish as steps ("simmer 20, rest 5" is a dish of 25 min params: dishes*, readyInMinutes, readyAt, startNow, timeZone |
meal_status | Say what is next in a meal plan made with plan_meal, and how long until it. Give the plan's code (the last part of its link). Only reads; never changes a plan. Give the control key too, if you have it, to also see the timers on the phone. params: code*, key |
pause_meal | Pause every dish of this plan that is running on the phone (the cook can resume on the phone or you can call resume_meal). Needs the plan's code and control key. Only works after the person has tapped Start on the phone; before that it says so. params: code*, key* |
resume_meal | Resume the paused dishes of this plan on the phone. Needs the plan's code and control key. params: code*, key* |
adjust_dish | Add time to a dish (a positive number of minutes) or take time off (negative). Before the person taps Start this changes the plan, and the ready time stays; afterwards it changes that dish's timer on the phone. Needs the plan's code and control key. params: code*, key*, dish*, minutes* |
skip_step | Skip the rest of the current wait for one dish: a dish still waiting to go in starts now, and a dish that is cooking finishes now. Only works after the person has tapped Start on the phone. Needs the plan's code and control key. params: code*, key*, dish* |
add_dish | Add one more dish to this plan. The ready time stays, so the new dish goes in at the ready time minus its cooking time and must still fit. Before the person taps Start it joins the plan on the sheet; afterwards it goes onto the phone too. Same rules as plan_meal: a plain-text name, at most 12 dishes. Needs the plan's code and control key. params: code*, key*, name*, minutes*, steps |
link_dish | Make a dish start a while after another dish goes in or is done ("the potatoes 30 minutes after the chicken goes in"), or clear that link by leaving `after` out. Starting the other dish early or late then moves this one with it. A dish cannot wait on a dish that waits on it, and a dish that already started cannot be linked. Needs the plan's code and control key. params: code*, key*, dish*, after, when, minutes |
cancel_meal | Cancel this plan: its link stops working, and if the person already started it, its timers are removed from the phone. Only that plan's timers; nothing else on the phone. Needs the plan's code and control key. Ask the person first. params: code*, key* |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.