ThawDay

com.thawday/thawdaythawday.comstreamable-httpv1.0.3Scanned 3 hours ago

Turkey thaw, roast, and food-safety timelines calculated for your bird's weight and dates.

3 tools: 1 change things and 2 only read.

Reads private data · 0
Reads text others write · 0
Can send data out · 0
No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 1Creates or changes something that can be changed back.Claude Code: ask

plan_turkey_timelineThawDay counts back from your dinner hour and names the exact buy, thaw, brine, and roast days.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
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.
Annotations the server declares
- title: Plan the turkey timeline
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

Only reads 2Looks things up and changes nothing.Show 2 read-only tools

get_roast_timeDinner at 5 does not mean the oven at 5: for a big bird, the oven time lands hours earlier than most people picture.No findings
Why it is in this group
- The name "get_roast_time" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: How long to roast
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_thaw_timeThe thaw is where Thanksgiving goes wrong: guess the start day and the bird is still frozen on cook day.No findings
Why it is in this group
- The name "get_thaw_time" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: How long to thaw
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0: Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 5, 2026, 03:19 UTC, unchanged since Nov 5, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable: yes
HTTP status of an anonymous initialize: 200
tools/list served without credentials: yes
Tools that change things, listed without credentials: 1
Protocol version: 2025-06-18
WWW-Authenticate on 401: not observed
resource_metadata in WWW-Authenticate: not observed
RFC 9728 protected resource metadata: not observed
Authorization servers: not observed
Legacy HTTP+SSE transport: no
Dynamic client registration: not observed
Client ID metadata documents: not observed

WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
Matched text
https://mcp.thawday.com/mcp: tools/list returned 3 tools to an anonymous client, including plan_turkey_timeline (write)
What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http thawday https://mcp.thawday.com/mcp

claude mcp add --transport http thawday https://mcp.thawday.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__thawday__get_thaw_time",
      "mcp__thawday__get_roast_time"
    ],
    "ask": [
      "mcp__thawday__plan_turkey_timeline"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as thawday. Review it before you use it.

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/com.thawday/thawday/verify?hash=8054fe5ba61f818a0f9194b9f362ce8aa04849a60ef21b4167119d6380a389cb" | jq -e '.changed == false'

Pinned hash 8054fe5ba61f, from Nov 5, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.thawday/thawday/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/com.thawday/thawday.svg)](https://anlyon.dev/servers/com.thawday/thawday)

Source: MCP Registry · repository. Synced Nov 5, 2026, 04:18 UTC.