ThawDay
REMOTE · MCP.THAWDAY.COM
Turkey thaw, roast, and food-safety timelines calculated for your bird's weight and dates.
Available components
Last scanned (13 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1477 tokens (~492/item across 3 items; 3 tools + 0 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 Management53
- Stability observed for 16 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 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.
- 15 Nov 26 +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.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 7 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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://mcp.thawday.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thawday.com | CN=WE1,O=Google Trust Services,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e214b9ae851d5a40130eb10505c1c592 |
| SANs: thawday.com, mcp.thawday.com, *.mcp.thawday.com | ||||||
| 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 mcp.thawday.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| thawday.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.thawday.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.thawday.com/mcp | Inconclusive | 405 |
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 →
get_roast_time How long to roast ~257
Dinner at 5 does not mean the oven at 5: for a big bird, the oven time lands hours earlier than most people picture. The USDA roast time for an unstuffed turkey at 325F: the chart band and the middle of the band a plan should use, plus the oven-in time when a dinner date and time are given. With state frozen, it gives the USDA from-frozen chart band instead (cooking from frozen is safe and takes at least 50 percent longer). Covers 8 to 24 lb. Ends with the 165F check rule.
| Name | Type | Req | Description |
|---|---|---|---|
| dinner_date | string | – | Optional dinner date, YYYY-MM-DD. Default when a time is given: the next upcoming turkey day (Thanksgiving, or Dec 25 once Thanksgiving has passed). |
| dinner_time | string | – | Optional dinner time, 24-hour HH:MM. With a dinner time, the tool returns when the bird goes in the oven. |
| state | string | – | Whether the bird is thawed or still frozen. Default: thawed. Frozen uses the USDA from-frozen roast chart. |
| weight_lb | number | yes | Turkey weight in pounds, 8 to 24. Example: 18 |
No output schema declared.
No examples provided.
get_thaw_time How long to thaw ~260
The thaw is where Thanksgiving goes wrong: guess the start day and the bird is still frozen on cook day. This names the exact start day. How long a turkey takes to thaw, by USDA method: in the fridge (chart band in days, plus the start date when a cook date is given) or in cold water (30 minutes per pound, with the chart band in hours). Covers 8 to 24 lb.
| Name | Type | Req | Description |
|---|---|---|---|
| cook_date | string | – | Optional cook date, YYYY-MM-DD. With a fridge thaw, the tool returns the date to move the bird to the fridge. |
| cook_time | string | – | Optional cook time, 24-hour HH:MM. Default: 17:00. For a fridge thaw, give the dinner time the plan counts back from (the same frame as plan_turkey_timeline); the answer states the real time the bird… |
| method | string | – | Thaw method. Default: fridge. |
| weight_lb | number | yes | Turkey weight in pounds, 8 to 24. Example: 20 |
No output schema declared.
No examples provided.
plan_turkey_timeline Plan the turkey timeline ~403
ThawDay counts back from your dinner hour and names the exact buy, thaw, brine, and roast days. Build the dated turkey plan for one dinner: when to buy, when to start the fridge thaw, when to start brining (if brining), when the bird goes in the oven at 325F, when to start the sides, and when to rest and carve. Dates come from USDA FSIS thaw and roast charts. Plans unstuffed birds, 8 to 24 lb. Dinner times are read in local time, just as they were given. Steps that depend on the time now are judged in that local frame: pass an IANA timezone when you know it; without one, a step is only called past once it is past in every US time zone. The plan says so in a clock note.
| Name | Type | Req | Description |
|---|---|---|---|
| brining | string | – | Add a brine start row, 24 hours before the oven. Default: no. |
| dinner_date | string | – | Dinner date, YYYY-MM-DD. Default: the next upcoming turkey day (Thanksgiving, or Dec 25 once Thanksgiving has passed). |
| dinner_time | string | – | Dinner time, 24-hour HH:MM. Default: 17:00. |
| now_local | string | – | Optional: the user's current local date and time, like 2026-11-02 14:20. Wins over timezone when both are given. Most callers should pass timezone instead. |
| state | string | – | Whether the bird is frozen or fresh. Default: frozen. |
| timezone | string | – | Optional: the user's IANA time zone, like America/New_York. When given, steps are judged against the user's exact local time. When omitted, a step is called past only once it is past in every US time… |
| weight_lb | number | yes | Turkey weight in pounds, 8 to 24. Example: 14 |
No output schema declared.
No examples provided.
How do I install the ThawDay MCP server?
ThawDay is a hosted endpoint at https://mcp.thawday.com/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 · mcp.thawday.com
claude mcp add --transport http com-thawday-thawday 'https://mcp.thawday.com/mcp'
What is the ThawDay MCP server?
ThawDay is an MCP server listed in the public MCP registry as com.thawday/thawday. Turkey thaw, roast, and food-safety timelines calculated for your bird's weight and dates. This page covers its hosted endpoint (https://mcp.thawday.com/mcp).
Is the ThawDay MCP server safe to use?
ThawDay scores 69 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 ThawDay MCP server expose?
ThawDay exposes 3 tools: plan_turkey_timeline, get_thaw_time, get_roast_time. Their descriptions and schemas cost roughly 920 tokens of context every time the server is loaded.
Does the ThawDay MCP server require authentication?
No. We connected to ThawDay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ThawDay MCP server still maintained?
ThawDay 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 ThawDay MCP server?
VerifyMCP ran 12 checks on ThawDay, 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 ThawDay: 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.