Findings on what compounds and supplements do in the body, with evidence strength, quote and paper.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 699 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Other
Plan a meal and run kitchen timers that ring on your phone. No sign-in.
2 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 2 | 2 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Kitchen Timer
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http kitchen-timer https://kt.tnyforge.com/mcp/openCapabilities
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.
DiscoveredAdd 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.
DiscoveredCancel 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.
DiscoveredMake 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.
DiscoveredSay 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.
DiscoveredPause 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.
DiscoveredMake 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).
DiscoveredResume the paused dishes of this plan on the phone. Needs the plan's code and control key.
DiscoveredSkip 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 1780 ms | 9 |