Koskamo

ThawDay MCP

A read-only MCP server that calculates turkey thawing, brining, and roasting timelines based on weight, method, and dinner time using USDA food safety charts. It provides tools to plan a full dinner schedule, determine thaw duration, and calculate roast times without storing any user data.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

ThawDay MCP logo, by ThawDayVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by ThawDay
MCP endpoint (Streamable HTTP)
https://mcp.thawday.com/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

3 of 3 have a description · 3 of 3 declare behavior hints · 3 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to thawday.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Plan a full turkey dinner timeline including buy, thaw, brine, and roast dates
  • Calculate fridge or cold-water thaw time based on turkey weight
  • Determine roast time for a specific turkey weight at 325°F

Source and maintenance

Vendor evidenceRegistry 1.0.3
Maintenance checked

Protocol and capabilities

Server
thawday 1.0.2
MCP protocol negotiated in check
2025-06-18
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Guess when a turkey should start thawing: most people guess 2 days too late. ThawDay counts back from your dinner hour and names the exact buy, thaw, brine, and roast days. ThawDay plans turkey timing from fixed USDA Food Safety and Inspection Service charts (re-verified Oct 22, 2026). Use plan_turkey_timeline for the full dated plan (buy, thaw, brine, oven, sides, rest). Use get_thaw_time for a thaw question and get_roast_time for a roast question. For a bird cooked from frozen, use get_roast_time with state frozen: USDA says that is safe, takes at least 50 percent longer, and has its own chart. Every number in a tool result comes from those USDA charts or is labeled kitchen practice in the result itself. Never invent times, temperatures, or dates, and never change a number a tool returns. The tools plan unstuffed birds from 8 to 24 lb only. For a weight outside that range, say the tools cover 8 to 24 lb. All tools are read-only: they buy nothing, book nothing, price nothing, and hold no user data. There are no accounts and no saved plans. Food safety is USDA handling only: never thaw on the counter, and the bird is done at 165F in the thickest part of the breast, the innermost thigh, and the innermost wing. Do not give personal health or allergy advice. plan_turkey_timeline reads dinner times in the user's local time, just as the user gave them. It checks the time now on the server clock (UTC), but it only calls a step past once that step is past in every US time zone; if you know the user's IANA time zone, pass it as the timezone input and their local time is used exactly. Its result carries a clock note about that frame: pass the clock note on with the plan. When a thaw answer has no cook date, it carries a count_back line: pass it on, and ask for the cook date so you can call again and name the exact day. When a cold-water answer carries a start time, lead with it: the start time and the water-change count are the parts a person acts on. Hand every plan back as dated steps a cook can say out loud and repeat to someone else: the buy day, the fridge day, and the oven time. Three dates are the whole story. When a plan result carries a calendar_link, offer it with the plan: it opens this exact plan in the ThawDay calculator, where the cook can add it to their calendar (.ics), print it, or share it.

Tools

3 advertised

plan_turkey_timeline — Plan the turkey timeline
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

plan_turkey_timeline input schema
{
  "type": "object",
  "required": [
    "weight_lb"
  ],
  "properties": {
    "state": {
      "enum": [
        "frozen",
        "fresh"
      ],
      "type": "string",
      "description": "Whether the bird is frozen or fresh. Default: frozen."
    },
    "brining": {
      "enum": [
        "yes",
        "no"
      ],
      "type": "string",
      "description": "Add a brine start row, 24 hours before the oven. Default: no."
    },
    "timezone": {
      "type": "string",
      "description": "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 zone."
    },
    "now_local": {
      "type": "string",
      "description": "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."
    },
    "weight_lb": {
      "type": "number",
      "description": "Turkey weight in pounds, 8 to 24. Example: 14"
    },
    "dinner_date": {
      "type": "string",
      "description": "Dinner date, YYYY-MM-DD. Default: the next upcoming turkey day (Thanksgiving, or Dec 25 once Thanksgiving has passed)."
    },
    "dinner_time": {
      "type": "string",
      "description": "Dinner time, 24-hour HH:MM. Default: 17:00."
    }
  },
  "additionalProperties": false
}
plan_turkey_timeline annotations
{
  "title": "Plan the turkey timeline",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
get_thaw_time — How long to thaw
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_thaw_time input schema
{
  "type": "object",
  "required": [
    "weight_lb"
  ],
  "properties": {
    "method": {
      "enum": [
        "fridge",
        "cold_water"
      ],
      "type": "string",
      "description": "Thaw method. Default: fridge."
    },
    "cook_date": {
      "type": "string",
      "description": "Optional cook date, YYYY-MM-DD. With a fridge thaw, the tool returns the date to move the bird to the fridge."
    },
    "cook_time": {
      "type": "string",
      "description": "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 spends in the fridge before oven-in. For cold water, give the time the bird must be thawed by (when it goes in the oven), not the dinner time."
    },
    "weight_lb": {
      "type": "number",
      "description": "Turkey weight in pounds, 8 to 24. Example: 20"
    }
  },
  "additionalProperties": false
}
get_thaw_time annotations
{
  "title": "How long to thaw",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
get_roast_time — How long to roast
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_roast_time input schema
{
  "type": "object",
  "required": [
    "weight_lb"
  ],
  "properties": {
    "state": {
      "enum": [
        "thawed",
        "frozen"
      ],
      "type": "string",
      "description": "Whether the bird is thawed or still frozen. Default: thawed. Frozen uses the USDA from-frozen roast chart."
    },
    "weight_lb": {
      "type": "number",
      "description": "Turkey weight in pounds, 8 to 24. Example: 18"
    },
    "dinner_date": {
      "type": "string",
      "description": "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": {
      "type": "string",
      "description": "Optional dinner time, 24-hour HH:MM. With a dinner time, the tool returns when the bird goes in the oven."
    }
  },
  "additionalProperties": false
}
get_roast_time annotations
{
  "title": "How long to roast",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
180 ms
95th percentile latency
180 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 180 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http thawday-mcp https://mcp.thawday.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add thawday-mcp --url https://mcp.thawday.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable thawday-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "thawday-mcp": {
      "url": "https://mcp.thawday.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "thawday-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.thawday.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start thawday-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "thawday-mcp": {
      "type": "http",
      "url": "https://mcp.thawday.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http thawday-mcp https://mcp.thawday.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.thawday.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "thawday-mcp": {
      "serverUrl": "https://mcp.thawday.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like ThawDay MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run ThawDay MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing