Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Zovo Cooking Timeline

REMOTE · COOKING-TIMELINE.ZOVO.ONE

Holiday cooking schedule

+4 this week 79 Trust /100

Last scanned (18 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability70
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 10 Nov 26 +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.

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 73

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://cooking-timeline.zovo.one/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zovo.one CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 1a6be51dae225a780e14b5b59cd24fa3
SANs: zovo.one, *.zovo.one
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of cooking-timeline.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cooking-timeline.zovo.one/mcp Verified 200
http (plaintext) http://cooking-timeline.zovo.one/mcp HTTPS enforced 301 https://cooking-timeline.zovo.one/mcp
MCP tools · 2 exposed · ~949 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
calculate_turkey_times ~246

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.

NameTypeReqDescription
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–yesTurkey weight in pounds, or text with a unit, e.g. 14 or "6.5 kg".
NameTypeReqDescription
cold_water_thaw_minutesnumberyes–
fridge_thaw_days_highnumberyes–
fridge_thaw_days_lownumberyes–
notesarrayyes–
oven_temp_fnumberyes–
roast_minutes_highnumberyes–
roast_minutes_lownumberyes–
roast_timestringyes–
safe_internal_temp_cnumberyes–
safe_internal_temp_fnumberyes–
schedule–yes–
sourcestringyes–
stuffedbooleanyes–
usda_bracketstringyes–
weight_kgnumberyes–
weight_lbnumberyes–

No examples provided.

plan_cooking_timeline ~703

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.

NameTypeReqDescription
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}.
NameTypeReqDescription
assumptionsarrayyes–
conflictsarrayyes–
conflicts_countobject––
countsobjectyes–
dishesarrayyes–
dishes_countobject––
downloadsobjectyes–
flagsarrayyes–
flags_countobject––
heldarrayyes–
movedarrayyes–
ovensnumberyes–
plan_notesarrayyes–
serveobjectyes–
shared_ovenarrayyes–
shoppingobjectyes–
stepsarrayyes–
steps_countobject––
stovetoparrayyes–
titlestringyes–
turkeyarrayyes–

No examples provided.

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.

remote · cooking-timeline.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-cooking-timeline 'https://cooking-timeline.zovo.one/mcp'
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.