Skip to content

FeastFlow cooking times MCP server

uk.co.feastflow/cooking-timesfeastflow.co.ukstreamable-httpv1.0.1Scanned

Turkey and roast cooking times, thawing times and roast dinner timelines. UK and US times.

5 tools: 5 change things.

Tools: 0 delete, 0 irreversible, 5 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • 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.dev only lists and labels, and these labels are the same either way.

What the FeastFlow cooking times MCP server can do

The FeastFlow cooking times MCP server is published by feastflow.co.uk, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: turkey_cooking_time, turkey_thawing_time, roast_cooking_time, plan_roast_dinner and 1 more), but cannot delete data. None of its tools only reads.

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

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 9, 2026, version 1.0.1.

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.

5 tools

Changes things 5Claude Code: ask
  • plan_roast_dinnerA timeline for a whole roast dinner (Sunday roast, Christmas dinner or Thanksgiving), worked back from the serving time: when to take the meat out of the fridge, heat the oven, put…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    A timeline for a whole roast dinner (Sunday roast, Christmas dinner or Thanksgiving), worked back from the serving time: when to take the meat out of the fridge, heat the oven, put it in, turn the oven up for the sides, and when each side goes on. Also lists what can be done the day before.

    Annotations the server declares

    • title: Plan a roast dinner
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • roast_cooking_timeHow long to roast beef, lamb, pork, chicken or gammon by weight, with the oven temperature, resting time, the temperature to take it out at and a tip.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How long to roast beef, lamb, pork, chicken or gammon by weight, with the oven temperature, resting time, the temperature to take it out at and a tip. Beef can be rare, medium or well done; lamb pink or well done; lamb and pork shoulder are slow roasted; gammon can be roasted or simmered. Give a serving time to get when it goes in.

    Annotations the server declares

    • title: Roast cooking time
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • side_dish_timesCooking times and oven temperatures for roast, baked, mashed and new potatoes, Yorkshire puddings, and chicken breasts, thighs, drumsticks, wings and legs.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Cooking times and oven temperatures for roast, baked, mashed and new potatoes, Yorkshire puddings, and chicken breasts, thighs, drumsticks, wings and legs.

    Annotations the server declares

    • title: Side dish times
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • turkey_cooking_timeHow long to roast a turkey by weight: cooking time, oven temperature, resting time and the temperature it must reach.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How long to roast a turkey by weight: cooking time, oven temperature, resting time and the temperature it must reach. Covers a whole turkey, a crown (breast on the bone) or a boneless breast joint, with UK (British Turkey, 190°C) or US (USDA, 325°F) times. Give a serving time to get when it goes in the oven.

    Annotations the server declares

    • title: Turkey cooking time
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • turkey_thawing_timeHow long a frozen turkey takes to thaw in the fridge (about 12 hours per kg) or in cold water (30 minutes per lb), and, given the day you will cook it, which day to move it from th…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How long a frozen turkey takes to thaw in the fridge (about 12 hours per kg) or in cold water (30 minutes per lb), and, given the day you will cook it, which day to move it from the freezer to the fridge.

    Annotations the server declares

    • title: Turkey thawing time
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • 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 10, 2026, 08:20 UTC, unchanged since Nov 10, 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
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

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

    Matched text

    https://feastflow.co.uk/mcp: tools/list returned 5 tools to an anonymous client, including turkey_cooking_time (write), turkey_thawing_time (write), roast_cooking_time (write), plan_roast_dinner (write), side_dish_times (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http cooking-times https://feastflow.co.uk/mcp
claude mcp add --transport http cooking-times https://feastflow.co.uk/mcp

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__cooking-times__turkey_cooking_time",
      "mcp__cooking-times__turkey_thawing_time",
      "mcp__cooking-times__roast_cooking_time",
      "mcp__cooking-times__plan_roast_dinner",
      "mcp__cooking-times__side_dish_times"
    ],
    "deny": []
  }
}

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 cooking-times. 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://anlyon.dev/api/v1/servers/uk.co.feastflow/cooking-times/verify?hash=f0dc207c3d6a408cdb1e18297fcbadbddf1b8e896e289b5061905aa9ce4960b5" | jq -e '.changed == false'

Pinned hash f0dc207c3d6a, from Nov 9, 2026, 18:18 UTC.

Watch

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

https://anlyon.dev/servers/uk.co.feastflow/cooking-times/changes.xml

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

Badge

anlyon.dev badge for uk.co.feastflow/cooking-times
[![anlyon.dev](https://anlyon.dev/badge/uk.co.feastflow/cooking-times.svg)](https://anlyon.dev/servers/uk.co.feastflow/cooking-times)

Source: MCP Registry. Synced Nov 9, 2026, 18:18 UTC.

FeastFlow cooking times MCP server: questions and answers

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

Is the FeastFlow cooking times MCP server safe?

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

Can the FeastFlow cooking times MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the FeastFlow cooking times 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 FeastFlow cooking times MCP server have?

5 tools: 5 write. turkey_cooking_time, turkey_thawing_time, roast_cooking_time, plan_roast_dinner and side_dish_times.

Does the FeastFlow cooking times MCP server need sign-in or OAuth?

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

Does the FeastFlow cooking times MCP server send data to outside services?

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

Has the FeastFlow cooking times MCP server changed its tools?

Not since anlyon.dev started tracking it. Last scanned Nov 9, 2026.