Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Kitchen Timer is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
Plan a meal and run kitchen timers that ring on your phone. No sign-in.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http kitchen-timer-mcp https://kt.tnyforge.com/mcp/open
# 2 — ask your agent for something these tools do
# plan_meal, meal_status, pause_meal and 6 more
Kitchen Timer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TNAll 1 server
tnyforge1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http kitchen-timer-mcp https://kt.tnyforge.com/mcp/openReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dishes | array | yes | What is being cooked. A single timer is one dish. |
| readyInMinutes | number | no | Everything ready this many minutes from now. Give exactly one of readyInMinutes, readyAt, startNow. |
| readyAt | string/number | no | Everything ready at this time: ISO 8601 with a UTC offset (2026-10-17T19:00:00+01:00), or without an offset when timeZone is given, or epoch milliseconds. |
| startNow | boolean | no | True: start every dish now (the longest dish sets when it is ready). |
| timeZone | string | no | Optional IANA time zone such as Europe/London. Only used to word the schedule text; the card and the phone show times in the viewer's own clock. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The plan's code, or its whole link. |
| key | string | no | Optional: the plan's secret control key. With it the answer also says whether the person has started the timers on the phone and what each one is doing. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The plan's code, or its whole link. |
| key | string | yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. |
Resume the paused dishes of this plan on the phone. Needs the plan's code and control key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The plan's code, or its whole link. |
| key | string | yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The plan's code, or its whole link. |
| key | string | yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. |
| dish | string | yes | The dish's name as in the plan, or its number in the plan (1 is the first dish). |
| minutes | number | yes | Minutes to add (positive) or take off (negative), such as 2 or -1.5. Not zero. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The plan's code, or its whole link. |
| key | string | yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. |
| dish | string | yes | The dish's name as in the plan, or its number in the plan (1 is the first 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The plan's code, or its whole link. |
| key | string | yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. |
| name | string | yes | Plain text, 80 characters at most. |
| minutes | number | yes | Total cooking time in minutes. |
| steps | array | no | Optional moments inside the cooking time. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The plan's code, or its whole link. |
| key | string | yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. |
| dish | string | yes | The dish's name as in the plan, or its number in the plan (1 is the first dish). |
| after | string/number | no | The dish to follow: its name as in the plan, or its number. Leave out to clear this dish's link. |
| when | string | no | Count from when that dish goes in, or from when it is done. |
| minutes | number | no | Minutes after that moment. 0 or left out: right then. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The plan's code, or its whole link. |
| key | string | yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Kitchen Timer or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestb353e5fa170368341eb5603f1d60c9c99ac057caa9a4c34731c895bb23b1ddd9
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| plan_meal | state-write | state-write: declares readOnlyHint: false |
| meal_status | no tags | |
| pause_meal | state-write | state-write: declares readOnlyHint: false |
| resume_meal | state-write | state-write: declares readOnlyHint: false |
| adjust_dish | state-write | state-write: declares readOnlyHint: false |
| skip_step | state-write | state-write: declares readOnlyHint: false |
| add_dish | state-write | state-write: declares readOnlyHint: false |
| link_dish | state-write | state-write: declares readOnlyHint: false |
| cancel_meal | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestb353e5fa17036834
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Kitchen Timer can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.