# Kitchen Timer (remote · kt.tnyforge.com)

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

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `kt.tnyforge.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-tnyforge-kitchen-timer/mcp-open.md), [page](https://verifymcp.io/servers/com-tnyforge-kitchen-timer/mcp-open)

## Channel facts

- Endpoint: `https://kt.tnyforge.com/mcp/open`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_meal).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-tnyforge-kitchen-timer 'https://kt.tnyforge.com/mcp/open'
```

### Cursor

```json
{
  "mcpServers": {
    "com-tnyforge-kitchen-timer": {
      "url": "https://kt.tnyforge.com/mcp/open"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-tnyforge-kitchen-timer": {
      "type": "http",
      "url": "https://kt.tnyforge.com/mcp/open"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-tnyforge-kitchen-timer]
url = "https://kt.tnyforge.com/mcp/open"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-tnyforge-kitchen-timer": {
      "type": "remote",
      "url": "https://kt.tnyforge.com/mcp/open",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-tnyforge-kitchen-timer --url 'https://kt.tnyforge.com/mcp/open' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-tnyforge-kitchen-timer:
    url: "https://kt.tnyforge.com/mcp/open"
```

### Netclaw

```json
{
  "McpServers": {
    "com-tnyforge-kitchen-timer": {
      "Transport": "http",
      "Url": "https://kt.tnyforge.com/mcp/open"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-tnyforge-kitchen-timer -t streamable-http -u 'https://kt.tnyforge.com/mcp/open'
```

### Other

```json
{
  "mcpServers": {
    "com-tnyforge-kitchen-timer": {
      "type": "http",
      "url": "https://kt.tnyforge.com/mcp/open"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 66, +1)

- [functional] Server version: kt-v87 → kt-v89

### 2026-10-23 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: kt-v84 → kt-v87

### 2026-10-22 (score 65)

First indexed and scored.

## MCP tools (8)

### `plan_meal` (~522 tokens)

Plan a 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).

Input parameters:

- `dishes` (array, required): 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.

Output parameters:

- `alarms` (string)
- `code` (string)
- `dishes` (array)
- `expiresAtMs` (integer)
- `readyAtMs` (integer)
- `schedule` (array)
- `serverNowMs` (integer)
- `url` (string): Open this on the phone in the kitchen.

### `meal_status` (~123 tokens)

What is next in a meal plan

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.

Input parameters:

- `code` (string, required): 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.

Output parameters:

- `claimed` (boolean): Only with the key: a phone has tapped Start.
- `code` (string)
- `next` (object|null)
- `readyAtMs` (integer)
- `serverNowMs` (integer)
- `state` (string)
- `timers` (array): Only with the key, once the phone has started: each dish's state on the phone.
- `upcoming` (array)

### `pause_meal` (~115 tokens)

Pause the 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.

Input parameters:

- `code` (string, required): The plan's code, or its whole link.
- `key` (string, required): The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link.

Output parameters:

- `message` (string)

### `resume_meal` (~80 tokens)

Resume the meal

Resume the paused dishes of this plan on the phone. Needs the plan's code and control key.

Input parameters:

- `code` (string, required): The plan's code, or its whole link.
- `key` (string, required): The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link.

Output parameters:

- `message` (string)

### `adjust_dish` (~174 tokens)

Add or take off time

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.

Input parameters:

- `code` (string, required): The plan's code, or its whole link.
- `dish` (string, required): The dish's name as in the plan, or its number in the plan (1 is the first dish).
- `key` (string, required): 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, required): Minutes to add (positive) or take off (negative), such as 2 or -1.5. Not zero.

Output parameters:

- `message` (string)

### `skip_step` (~138 tokens)

Skip ahead on a dish

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.

Input parameters:

- `code` (string, required): The plan's code, or its whole link.
- `dish` (string, required): The dish's name as in the plan, or its number in the plan (1 is the first dish).
- `key` (string, required): The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link.

Output parameters:

- `message` (string)

### `add_dish` (~180 tokens)

Add a dish to the plan

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.

Input parameters:

- `code` (string, required): The plan's code, or its whole link.
- `key` (string, required): 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, required): Total cooking time in minutes.
- `name` (string, required): Plain text, 80 characters at most.
- `steps` (array): Optional moments inside the cooking time.

Output parameters:

- `message` (string)

### `cancel_meal` (~111 tokens)

Cancel the 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.

Input parameters:

- `code` (string, required): The plan's code, or its whole link.
- `key` (string, required): The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link.

Output parameters:

- `message` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-tnyforge-kitchen-timer/mcp-open#diagnostics

## Score history

- 2026-10-24: 66
- 2026-10-23: 65
- 2026-10-22: 65

## Common questions

### 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.

## Links

- Remote endpoint: https://kt.tnyforge.com/mcp/open
- Website: https://kt.tnyforge.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-tnyforge-kitchen-timer/mcp-open.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-tnyforge-kitchen-timer/mcp-open.json
- HTML version of this page: https://verifymcp.io/servers/com-tnyforge-kitchen-timer/mcp-open