# FeastFlow cooking times (remote · feastflow.co.uk)

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

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `feastflow.co.uk`: 70/100 (this document), [markdown](https://verifymcp.io/servers/uk-co-feastflow-cooking-times/feastflow.md), [page](https://verifymcp.io/servers/uk-co-feastflow-cooking-times/feastflow)

## Channel facts

- Endpoint: `https://feastflow.co.uk/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1485 tokens (~247/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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.

## Install

### How do I install the FeastFlow cooking times MCP server?

FeastFlow cooking times is a hosted endpoint at https://feastflow.co.uk/mcp, 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 uk-co-feastflow-cooking-times 'https://feastflow.co.uk/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "uk-co-feastflow-cooking-times": {
      "url": "https://feastflow.co.uk/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uk-co-feastflow-cooking-times": {
      "type": "http",
      "url": "https://feastflow.co.uk/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.uk-co-feastflow-cooking-times]
url = "https://feastflow.co.uk/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-co-feastflow-cooking-times": {
      "type": "remote",
      "url": "https://feastflow.co.uk/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add uk-co-feastflow-cooking-times --url 'https://feastflow.co.uk/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uk-co-feastflow-cooking-times:
    url: "https://feastflow.co.uk/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "uk-co-feastflow-cooking-times": {
      "Transport": "http",
      "Url": "https://feastflow.co.uk/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add uk-co-feastflow-cooking-times -t streamable-http -u 'https://feastflow.co.uk/mcp'
```

### Other

```json
{
  "mcpServers": {
    "uk-co-feastflow-cooking-times": {
      "type": "http",
      "url": "https://feastflow.co.uk/mcp"
    }
  }
}
```

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-11-21 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 66, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1127 → 1485
- [functional] Server version: 1.0.1 → 1.1.0
- [functional] New tool “food_cooking_time”

### 2026-11-10 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 64)

First indexed and scored.

## MCP tools (6)

### `turkey_cooking_time` (~257 tokens)

Turkey cooking time

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.

Input parameters:

- `cut` (string): whole (default), crown, or breast for a boneless joint or roll.
- `method` (string): uk: 190°C (170°C fan), 375°F. usda: 325°F (165°C). Defaults to usda when the weight is in lb, otherwise uk.
- `serve_time` (string): Optional serving time as HH:MM in 24-hour time, e.g. 14:00. When given, the answer says when it goes in the oven.
- `stuffed` (boolean): A whole bird stuffed in the cavity (USDA times only; for UK times, weigh it with the stuffing).
- `unit` (string): kg (default) or lb.
- `weight` (number, required): Weight of the meat, in the unit given by unit.

### `turkey_thawing_time` (~144 tokens)

Turkey thawing time

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.

Input parameters:

- `cook_date` (string): Optional day you will cook it, as YYYY-MM-DD, e.g. 2026-12-25 or 2026-11-26.
- `method` (string): fridge (default) or water.
- `unit` (string): kg (default) or lb.
- `weight` (number, required): Weight of the meat, in the unit given by unit.

### `roast_cooking_time` (~229 tokens)

Roast cooking time

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.

Input parameters:

- `cut` (string): Optional. beef: joint. lamb: leg or shoulder. pork: loin, shoulder or belly. chicken: whole. gammon: oven or boil.
- `doneness` (string): Optional. beef: rare, medium or well. lamb: pink or well.
- `meat` (string, required)
- `serve_time` (string): Optional serving time as HH:MM in 24-hour time, e.g. 14:00. When given, the answer says when it goes in the oven.
- `unit` (string): kg (default) or lb.
- `weight` (number, required): Weight of the meat, in the unit given by unit.

### `plan_roast_dinner` (~302 tokens)

Plan a roast dinner

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.

Input parameters:

- `doneness` (string): Optional. beef: rare, medium or well. lamb: pink or well.
- `main` (string, required): The main roast. crown is a turkey crown.
- `method` (string): Turkey only: uk (190°C) or usda (325°F). Defaults to usda when the weight is in lb.
- `serve_time` (string, required): Serving time as HH:MM in 24-hour time, e.g. 14:00.
- `sides` (array): Optional sides: roastPotatoes, yorkshires, pigsInBlankets, stuffing, rootVeg (roast parsnips and carrots), cauliflowerCheese, greens, carrots, breadSauce, mash, dressing (baked stuffing), greenBean (…
- `unit` (string): kg (default) or lb.
- `weight` (number, required): Weight of the meat, in the unit given by unit.

### `side_dish_times` (~73 tokens)

Potato, Yorkshire pudding and chicken piece times

Cooking times and oven temperatures for roast, baked, mashed and new potatoes, Yorkshire puddings, and chicken breasts, thighs, drumsticks, wings and legs.

Input parameters:

- `query` (string): Optional word to narrow the list, e.g. "roast", "yorkshire" or "thighs".

### `food_cooking_time` (~303 tokens)

Cooking time for any food and method

How long to cook a food, and at what temperature, by method: oven, air fryer, boil, steam, microwave, pan-fry, deep-fry, grill (broil), barbecue, slow cooker, pressure cooker, poach or braise. Covers over 100 foods: vegetables (broccoli, carrots, sprouts, asparagus, corn on the cob, butternut squash…), potatoes and chips, chicken breasts, thighs and wings, steak, burgers, mince, pork chops, sausages, bacon, lamb chops, salmon, cod, prawns, eggs, rice, pasta, halloumi, tofu and frozen food such as oven chips, nuggets and fish fingers. Gives the time for a typical portion, the temperature (°C, fan, °F, gas mark), how to do it, how to tell it is done and the safe temperature for meat and fish. Leave out the method to get every method for that food.

Input parameters:

- `food` (string, required): The food, in plain words, e.g. "broccoli", "chicken thighs", "frozen chips", "salmon", "boiled eggs".
- `method` (string): Optional: oven, air fryer, boil, steam, microwave, pan, deep fry, grill, barbecue, slow cooker, pressure cooker, poach or braise. Plain words like "roast", "Instant Pot" or "stir-fry" work too.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/uk-co-feastflow-cooking-times/feastflow#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 68
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 66
- 2026-11-12: 66
- 2026-11-11: 65
- 2026-11-10: 65
- 2026-11-09: 64

## Common questions

### What is the FeastFlow cooking times MCP server?

FeastFlow cooking times is an MCP server listed in the public MCP registry as uk.co.feastflow/cooking-times. Turkey and roast cooking times, thawing times and roast dinner timelines. UK and US times. This page covers its hosted endpoint (https://feastflow.co.uk/mcp).

### Is the FeastFlow cooking times MCP server safe to use?

FeastFlow cooking times scores 70 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 FeastFlow cooking times MCP server expose?

FeastFlow cooking times exposes 6 tools: turkey_cooking_time, turkey_thawing_time, roast_cooking_time, plan_roast_dinner, side_dish_times, food_cooking_time. Their descriptions and schemas cost roughly 1,308 tokens of context every time the server is loaded.

### Does the FeastFlow cooking times MCP server require authentication?

No. We connected to FeastFlow cooking times without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FeastFlow cooking times MCP server still maintained?

FeastFlow cooking times is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the FeastFlow cooking times MCP server?

VerifyMCP ran 12 checks on FeastFlow cooking times, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about FeastFlow cooking times: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://feastflow.co.uk/mcp
- Website: https://feastflow.co.uk/use-with-ai
- Changelog RSS feed: https://verifymcp.io/servers/uk-co-feastflow-cooking-times/feastflow.xml
- Changelog JSON feed: https://verifymcp.io/servers/uk-co-feastflow-cooking-times/feastflow/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/uk-co-feastflow-cooking-times/feastflow.json
- HTML version of this page: https://verifymcp.io/servers/uk-co-feastflow-cooking-times/feastflow
