# Zovo Cooking Timeline (remote · cooking-timeline.zovo.one)

Holiday cooking schedule

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

## Components

- remote · `cooking-timeline.zovo.one`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-cooking-timeline/cooking-timeline.md), [page](https://verifymcp.io/servers/theluckystrike-cooking-timeline/cooking-timeline)

## Channel facts

- Endpoint: `https://cooking-timeline.zovo.one/mcp`
- 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-11-21.

- **Endpoint Security**: 80/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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 70/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 1042 tokens (~347/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Zovo Cooking Timeline MCP server?

Zovo Cooking Timeline is a hosted endpoint at https://cooking-timeline.zovo.one/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 theluckystrike-cooking-timeline 'https://cooking-timeline.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-cooking-timeline": {
      "url": "https://cooking-timeline.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-cooking-timeline": {
      "type": "http",
      "url": "https://cooking-timeline.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-cooking-timeline]
url = "https://cooking-timeline.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-cooking-timeline": {
      "type": "remote",
      "url": "https://cooking-timeline.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-cooking-timeline --url 'https://cooking-timeline.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-cooking-timeline:
    url: "https://cooking-timeline.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-cooking-timeline": {
      "Transport": "http",
      "Url": "https://cooking-timeline.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-cooking-timeline -t streamable-http -u 'https://cooking-timeline.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-cooking-timeline": {
      "type": "http",
      "url": "https://cooking-timeline.zovo.one/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 79, +1)

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

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

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

### 2026-11-17 (score 77, +1)

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

### 2026-11-15 (score 76, +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-13 (score 75, +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-10 (score 74, +1)

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

### 2026-11-09 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 73)

First indexed and scored.

## MCP tools (2)

### `plan_cooking_timeline` (~703 tokens)

Plan cooking timeline

Use this when the user wants a Thanksgiving cooking timeline, a holiday dinner cooking schedule or an oven schedule for several dishes. Convert the user's menu, pasted recipe notes or a photo of a menu into the dishes array (name, prep_minutes, cook_minutes, rest_minutes, method, oven_temp, make_ahead); use text only as a fallback. Works backward from serve_time (default Thanksgiving, 26 November 2026, 4:00 PM) and gives each step a clock time, detects oven conflicts (one oven by default, ovens: 2 for two), moves make-ahead dishes earlier, adds turkey roast and thaw steps from the USDA table when a turkey weight is given, and returns a printable checklist PDF, an ICS calendar file with a reminder per step, and a shopping-day note. Up to 25 dishes. Does not invent recipe times or give recipes.

Input parameters:

- `burners`: Stovetop burners, default 4.
- `clock`: 12h (default, 4:00 PM) or 24h (16:00).
- `cooks`: People doing hands-on prep at the same time, default 1.
- `dishes`: The menu as a list of dish objects. Convert the user's pasted menu, recipe notes or a photo of a menu into these fields. Example: [{"name":"Green bean casserole","prep_minutes":15,"cook_minutes":30,"…
- `hold_minutes`: Minutes a dish that is not make-ahead may come out early and wait covered to make room in the oven, default 30. 0 to never hold.
- `ovens`: Number of ovens, 1 (default) or 2.
- `paper`: PDF paper size: letter (default) or A4.
- `preheat_minutes`: Minutes to preheat or change oven temperature, default 15.
- `reminder_minutes`: Calendar alarm this many minutes before each step, default 5.
- `serve_date`: Serve date if given separately, e.g. 2026-11-26.
- `serve_time`: When dinner is served, e.g. "2026-11-26 16:00", "4:00 PM" or "Nov 26 5pm". Default date is Thanksgiving, 26 November 2026; default time 4:00 PM.
- `share_within_f`: A dish that is not make-ahead may join an oven already running within this many °F (cooked about 10% longer per 25°F lower), default 25. 0 to keep recipe temperatures.
- `shopping_days_before`: Shopping day this many days before serving, default 2.
- `temperature_unit`: F (default) or C for oven temperatures given without a unit.
- `text`: Fallback only: a pasted menu, one dish per line, e.g. "Stuffing: prep 20, bake 45 min at 350F, make ahead". Prefer dishes.
- `title`: Title for the PDF and calendar, e.g. Thanksgiving at Grandma's.
- `turkey`: Optional turkey roasted from the USDA timetable at 325°F, e.g. {"weight":16,"stuffed":false,"frozen":true}.

Output parameters:

- `assumptions` (array)
- `conflicts` (array)
- `conflicts_count` (object)
- `counts` (object)
- `dishes` (array)
- `dishes_count` (object)
- `downloads` (object)
- `flags` (array)
- `flags_count` (object)
- `held` (array)
- `moved` (array)
- `ovens` (number)
- `plan_notes` (array)
- `serve` (object)
- `shared_oven` (array)
- `shopping` (object)
- `steps` (array)
- `steps_count` (object)
- `stovetop` (array)
- `title` (string)
- `turkey` (array)

### `calculate_turkey_times` (~246 tokens)

Calculate turkey roast and thaw times

Use this when the user asks a turkey cooking time calculator question: how long to roast a turkey by weight (lb or kg), stuffed or unstuffed, or turkey thaw time in the fridge or cold water. Returns the USDA FSIS roasting range at 325°F, the 165°F safe internal temperature, fridge and cold-water thaw times and, with a serve time, the clock times to start thawing and roasting. Covers 4 to 24 lb (stuffed 8 to 24 lb). Does not cover other meats, deep frying or smoking.

Input parameters:

- `clock`: 12h (default) or 24h.
- `rest_minutes`: Minutes to rest before carving, default 30 (USDA says at least 20).
- `serve_time`: Optional serve time to get clock times, e.g. "2026-11-26 16:00" or "4 PM" (default date Thanksgiving, 26 November 2026).
- `stuffed`: true if stuffed. Default false.
- `weight` (required): Turkey weight in pounds, or text with a unit, e.g. 14 or "6.5 kg".

Output parameters:

- `cold_water_thaw_minutes` (number)
- `fridge_thaw_days_high` (number)
- `fridge_thaw_days_low` (number)
- `notes` (array)
- `oven_temp_f` (number)
- `roast_minutes_high` (number)
- `roast_minutes_low` (number)
- `roast_time` (string)
- `safe_internal_temp_c` (number)
- `safe_internal_temp_f` (number)
- `schedule`
- `source` (string)
- `stuffed` (boolean)
- `usda_bracket` (string)
- `weight_kg` (number)
- `weight_lb` (number)

## Diagnostics

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

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73

## Common questions

### What is the Zovo Cooking Timeline MCP server?

Zovo Cooking Timeline is an MCP server listed in the public MCP registry as io.github.theluckystrike/cooking-timeline. Holiday cooking schedule. This page covers its hosted endpoint (https://cooking-timeline.zovo.one/mcp).

### Is the Zovo Cooking Timeline MCP server safe to use?

Zovo Cooking Timeline scores 79 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 Zovo Cooking Timeline MCP server expose?

Zovo Cooking Timeline exposes 2 tools: plan_cooking_timeline, calculate_turkey_times. Their descriptions and schemas cost roughly 949 tokens of context every time the server is loaded.

### Does the Zovo Cooking Timeline MCP server require authentication?

No. We connected to Zovo Cooking Timeline without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo Cooking Timeline MCP server still maintained?

Zovo Cooking Timeline 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 Zovo Cooking Timeline MCP server?

VerifyMCP ran 14 checks on Zovo Cooking Timeline, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. 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://cooking-timeline.zovo.one/mcp
- Website: https://cooking-timeline.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-cooking-timeline/cooking-timeline.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-cooking-timeline/cooking-timeline/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-cooking-timeline/cooking-timeline.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-cooking-timeline/cooking-timeline
