Kitchen Timer
REMOTE · KT.TNYFORGE.COM
Plan a meal and run kitchen timers that ring on your phone. No sign-in.
Available components
Last scanned (7 minutes ago)
Scores higher than 55% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_meal). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1775 tokens (~197/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
- Server version: kt-v87 → kt-v89 functional
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: kt-v84 → kt-v87 functional
- 22 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://kt.tnyforge.com/mcp/open
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tnyforge.com | CN=YE2,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 69b6090c0b48aa666b9e24ca154eafd3bc6 |
| SANs: *.tnyforge.com, tnyforge.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of kt.tnyforge.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tnyforge.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kt.tnyforge.com/mcp/open | Verified | 200 | |
| http (plaintext) | http://kt.tnyforge.com/mcp/open | HTTPS enforced | 308 | https://kt.tnyforge.com/mcp/open |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_dish Add a dish to the plan ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| minutes | number | yes | Total cooking time in minutes. |
| name | string | yes | Plain text, 80 characters at most. |
| steps | array | – | Optional moments inside the cooking time. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
No examples provided.
adjust_dish Add or take off time ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The plan's code, or its whole link. |
| dish | string | yes | The dish's name as in the plan, or its number in the plan (1 is the first dish). |
| 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. |
| minutes | number | yes | Minutes to add (positive) or take off (negative), such as 2 or -1.5. Not zero. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
No examples provided.
cancel_meal Cancel the meal ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
No examples provided.
meal_status What is next in a meal plan ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The plan's code, or its whole link. |
| key | string | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| claimed | boolean | – | Only with the key: a phone has tapped Start. |
| code | string | yes | – |
| next | object|null | – | – |
| readyAtMs | integer | yes | – |
| serverNowMs | integer | – | – |
| state | string | yes | – |
| timers | array | – | Only with the key, once the phone has started: each dish's state on the phone. |
| upcoming | array | – | – |
No examples provided.
pause_meal Pause the meal ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
No examples provided.
plan_meal Plan a meal ~522
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).
| Name | Type | Req | Description |
|---|---|---|---|
| dishes | array | yes | What is being cooked. A single timer is one dish. |
| readyAt | string|number | – | 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. |
| readyInMinutes | number | – | Everything ready this many minutes from now. Give exactly one of readyInMinutes, readyAt, startNow. |
| startNow | boolean | – | True: start every dish now (the longest dish sets when it is ready). |
| timeZone | string | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| alarms | string | – | – |
| code | string | yes | – |
| dishes | array | – | – |
| expiresAtMs | integer | – | – |
| readyAtMs | integer | yes | – |
| schedule | array | yes | – |
| serverNowMs | integer | – | – |
| url | string | yes | Open this on the phone in the kitchen. |
No examples provided.
resume_meal Resume the meal ~80
Resume the paused dishes of this plan on the phone. Needs the plan's code and control key.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
No examples provided.
skip_step Skip ahead on a dish ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The plan's code, or its whole link. |
| dish | string | yes | The dish's name as in the plan, or its number in the plan (1 is the first dish). |
| 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 | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
No examples provided.
How do I install the Kitchen Timer MCP server?
Kitchen Timer is a hosted endpoint at https://kt.tnyforge.com/mcp/open, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · kt.tnyforge.com
claude mcp add --transport http com-tnyforge-kitchen-timer 'https://kt.tnyforge.com/mcp/open'
What is the Kitchen Timer MCP server?
Kitchen Timer is an MCP server listed in the public MCP registry as com.tnyforge/kitchen-timer. Plan a meal and run kitchen timers that ring on your phone. No sign-in. This page covers its hosted endpoint (https://kt.tnyforge.com/mcp/open).
Is the Kitchen Timer MCP server safe to use?
Kitchen Timer scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Kitchen Timer MCP server expose?
Kitchen Timer exposes 8 tools: plan_meal, meal_status, pause_meal, resume_meal, adjust_dish, and 3 more. Their descriptions and schemas cost roughly 1,443 tokens of context every time the server is loaded.
Does the Kitchen Timer MCP server require authentication?
No. We connected to Kitchen Timer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Kitchen Timer MCP server still maintained?
Kitchen Timer is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.