Skip to content

Kitchen Timer MCP server

com.tnyforge/kitchen-timertnyforge.comstreamable-httpv1.0.0Scanned

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

9 tools: 1 can delete or cancel things and 8 change things.

Tools: 1 delete, 0 irreversible, 8 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Kitchen Timer MCP server can do

The Kitchen Timer MCP server is published by tnyforge.com, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (1 tool: cancel_meal) and create or change data (8 tools: plan_meal, meal_status, pause_meal, resume_meal and 4 more). None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 1Claude Code: deny
  • cancel_mealCancel this plan: its link stops working, and if the person already started it, its timers are removed from the phone.No findings

    Why it is in this group

    • The name "cancel_meal" says "cancel": a word for removing or ending something.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Cancel the meal
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Changes things 8Claude Code: ask
  • add_dishAdd one more dish to this plan.No findings

    Why it is in this group

    • The name "add_dish" says "add": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Add a dish to the plan
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • adjust_dishAdd time to a dish (a positive number of minutes) or take time off (negative).No findings

    Why it is in this group

    • The description's first verb is "add": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Add or take off time
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • meal_statusSay what is next in a meal plan made with plan_meal, and how long until it.1 finding

    Why it is in this group

    • The name "meal_status" says "status": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "meal_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "meal_status" says "status": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: What is next in a meal plan
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • pause_mealPause every dish of this plan that is running on the phone (the cook can resume on the phone or you can call resume_meal).No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Pause the meal
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • plan_mealMake a meal plan: each dish starts at the right moment so everything is ready at the same time.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Plan a meal
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • resume_mealResume the paused dishes of this plan on the phone.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    Resume the paused dishes of this plan on the phone. Needs the plan's code and control key.

    Annotations the server declares

    • title: Resume the meal
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • skip_stepSkip 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.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Skip ahead on a dish
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:24 UTC, unchanged since Oct 30, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://kt.tnyforge.com/.well-known/oauth-protected-resource
Authorization servers
https://kt.tnyforge.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (1 destructive, 8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://kt.tnyforge.com/mcp/open: tools/list returned 9 tools to an anonymous client, including cancel_meal (destructive), plan_meal (write), meal_status (write), pause_meal (write), resume_meal (write) and 4 more

    What this check looks for

Posture changes

  1. Oct 30, 2026
    • Tools that change things, listed without credentials: 8 to 9

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "meal_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "meal_status" says "status": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 1 changed.+1 added~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 9.View diff
    • Tools that change things, listed without credentials: 8 to 9

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__kitchen-timer__plan_meal",
      "mcp__kitchen-timer__meal_status",
      "mcp__kitchen-timer__pause_meal",
      "mcp__kitchen-timer__resume_meal",
      "mcp__kitchen-timer__adjust_dish",
      "mcp__kitchen-timer__skip_step",
      "mcp__kitchen-timer__add_dish",
      "mcp__kitchen-timer__link_dish"
    ],
    "deny": [
      "mcp__kitchen-timer__cancel_meal"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as kitchen-timer. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.tnyforge/kitchen-timer/verify?hash=ac29972d5e5f0ed96a2a66b954750454a7a320bb2abce00f9491f09a9385ed87" | jq -e '.changed == false'

Pinned hash ac29972d5e5f, from Nov 8, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.tnyforge/kitchen-timer/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.tnyforge/kitchen-timer
[![Anlyon Radar](https://radar.anlyon.com/badge/com.tnyforge/kitchen-timer.svg)](https://radar.anlyon.com/servers/com.tnyforge/kitchen-timer)

Source: MCP Registry. Synced Oct 22, 2026, 22:17 UTC.

Kitchen Timer MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Kitchen Timer MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 9 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Kitchen Timer MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_meal.

Can the Kitchen Timer MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Kitchen Timer MCP server have?

9 tools: 1 destructive, 8 write. cancel_meal, plan_meal, meal_status, pause_meal, resume_meal, adjust_dish, skip_step, add_dish and 1 more.

Does the Kitchen Timer MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Kitchen Timer MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Kitchen Timer MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.