mcpbeat Sign in

Kitchen Timer MCP Server

by tnyforge Your server? Claim it
answering

Kitchen Timer is answering right now. Last checked 3 min ago. It exposes 8 tools.

Plan a meal and run kitchen timers that ring on your phone. No sign-in.

Uptime history 68 hours of history · worst hour 67%
68 hours agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
1238 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 9

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 23 October 2026. No other catalogue keeps this.

25 Oct a tool changed version5 times that day
24 Oct a tool changed version
23 Oct a tool changed version3 times that day
and 6 more, back to 23 October 2026

Kitchen Timer missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add kitchen-timer --transport http https://kt.tnyforge.com/mcp/open
Settings → Connectors → Add custom connector, then paste this address
https://kt.tnyforge.com/mcp/open
~/.codex/config.toml
[mcp_servers.kitchen-timer]
url = "https://kt.tnyforge.com/mcp/open"
.cursor/mcp.json
{
  "mcpServers": {
    "kitchen-timer": {
      "url": "https://kt.tnyforge.com/mcp/open"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "kitchen-timer": {
      "type": "http",
      "url": "https://kt.tnyforge.com/mcp/open"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

adjust
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.
cancel
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.
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.
meal
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.
pause
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.
plan
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 minutes with a step "Rest" at 20). If the person did not say when they want to eat, ASK before calling; use `readyInMinutes` for "we eat in 90 minutes", `readyAt` (an ISO date-time with a UTC offset, or local time plus `timeZone`) for "at 7", or `startNow` to start cooking now (a single timer is a one-dish plan with `startNow`). Keep times realistic and use only what the person gave you; at most 12 dishes and 12 hours. Dish names are plain text, no links. The reply link works for anyone who has it and the plan is deleted about a day after the meal. Tell the person the alarms ring on the phone page, not in this chat. The reply also holds a secret CONTROL KEY (starts with ktpk_): remember it for the rest of the chat, do not show it or put it in any link, and pass it with the plan's code to the control tools to keep managing this plan. Once it works you may offer the person to manage their whole kitchen from now on (⋯ → Link an agent in the app gives the connector address and a 6-digit code).
resume
resume_meal
Resume the paused dishes of this plan on the phone. Needs the plan's code and control key.
skip
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.

Endpoints

URLTransportStateLatencyChecked
https://kt.tnyforge.com/mcp/open streamable-http answering 932 ms 3 min ago

Alternatives to Kitchen Timer

same job, measured the same way
Stepladder
by stepladderapp

Put timed plans on the person's phone: steps, questions and waits that ring when a rest is over.

answering
Routine Run: write a routine
by routinerun

Write a step-by-step routine and get a link that opens it in Routine Run on iPhone. No sign-in.

3 tools answering
T
Twring
by twring

Your AI rings your phone or messages you on Twring when it needs you, and reads your reply.

answering
G
GetFit
by thegetfit

Build a workout that fits your time, gear and body — free, no sign-in.

5 tools answering
LFG Alarm
by lfg

Let your AI ring a real alarm on any phone or laptop, at any time or for any moment online.

answering
Final Check — A human checks your AI's work
by latentdatabank

A real person in Japan checks your AI's work and does what AI can't: phone calls, on-site photos.

answering
Symphony
by symphony

Plan meals around your diet and allergies, build a basket, and order Symphony meal kits in France.

answering
The Pantry Butler
by thepantrybutler

Answers 'what can I cook tonight?' from your own saved recipes and what's really in your kitchen.

6 tools answering

Kitchen Timer — questions

Answers built from our own checks of this server.

What can Kitchen Timer do?
It exposes 8 tools, read directly from the server on our last check. Among them: add_dish, adjust_dish, cancel_meal, meal_status, pause_meal, plan_meal and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Kitchen Timer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1238 ms. The bar chart above shows every period we have measured.
How do I connect Kitchen Timer?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Kitchen Timer need an API key?
No. Kitchen Timer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Kitchen Timer?
It answers our handshake in 1238 ms on average, which is faster than 2% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.