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.

Last Frost Date and Hardiness Zone MCP

REMOTE · LAST-FROST-DATE-HARDINESS-ZONE-MCP.LIPMICHAL.WORKERS.DEV

Last frost dates, USDA hardiness zone by ZIP, frost forecast and a vegetable planting calendar.

67 Trust /100

Last scanned (15 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

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 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
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 822 tokens (~205/item across 4 items; 4 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 Management13
  • Stability observed for 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

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 →

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 65

    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://last-frost-date-hardiness-zone-mcp.lipmichal.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lipmichal.workers.dev CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 ebf145553d5751d20e0d3cd51e3d7a94
SANs: lipmichal.workers.dev, *.lipmichal.workers.dev
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 last-frost-date-hardiness-zone-mcp.lipmichal.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. 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://last-frost-date-hardiness-zone-mcp.lipmichal.workers.dev/mcp Verified 200
http (plaintext) http://last-frost-date-hardiness-zone-mcp.lipmichal.workers.dev/mcp Inconclusive 405
MCP tools · 4 exposed · ~699 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
frost_dates ~209

Average (median) last spring frost date and first fall frost date for a US ZIP code, a place name or coordinates, the dates beaten in only 1 year in 10, the earliest and latest on record, the median frost-free growing season, and the last spring and first fall frost of the latest seasons. Computed from 30 complete seasons of daily minimum temperatures. threshold_f 32 (frost, default), 36 (light frost on tender plants) or 28 (hard freeze).

NameTypeReqDescription
latitudenumber–Latitude, instead of location.
locationstring–A US ZIP code ("80202"), a place ("Burlington, VT", "Leeds, UK") or "lat,lon". Add the state or country to a place name to avoid a same-named town.
longitudenumber–Longitude, instead of location.
threshold_fnumber–Frost threshold in F: 32 (default), 36 or 28.

No output schema declared.

No examples provided.

frost_forecast ~180

Forecast frost and freeze nights for the next 1 to 16 days (default 16) at a ZIP code, place or coordinates: each night at or below 36 F with its category (frost possible, frost or light freeze, freeze, hard freeze), the first night at or below 32 F and the coldest night. Answers "will it frost tonight".

NameTypeReqDescription
daysinteger–Days ahead, 1 to 16. Default 16.
latitudenumber–Latitude, instead of location.
locationstring–A US ZIP code ("80202"), a place ("Burlington, VT", "Leeds, UK") or "lat,lon". Add the state or country to a place name to avoid a same-named town.
longitudenumber–Longitude, instead of location.

No output schema declared.

No examples provided.

hardiness_zone ~93

The USDA plant hardiness zone for a US ZIP code from the 2023 USDA Plant Hardiness Zone Map (for example 6a), the average annual coldest winter temperature range it stands for in F and C, and the ZIP's coordinates. Answers "what growing zone am I in".

NameTypeReqDescription
zipstringyes5-digit US ZIP code, for example "80202" or "05401".

No output schema declared.

No examples provided.

planting_calendar ~217

When to plant vegetables at a ZIP code, place or coordinates: dates to start seeds indoors, transplant outdoors, direct sow and sow a fall crop, counted from the local median last spring and first fall frost, and whether a warm-season crop fits the frost-free season. Crops: tomato, pepper, eggplant, cucumber, zucchini, pumpkin, watermelon, corn, beans, basil, lettuce, spinach, peas, radish, carrot, beet, broccoli, cabbage, kale, onion, potato, cilantro, garlic. Default all.

NameTypeReqDescription
cropsarray–Crop names, for example ["tomato", "peas", "garlic"]. Default all.
latitudenumber–Latitude, instead of location.
locationstring–A US ZIP code ("80202"), a place ("Burlington, VT", "Leeds, UK") or "lat,lon". Add the state or country to a place name to avoid a same-named town.
longitudenumber–Longitude, instead of location.

No output schema declared.

No examples provided.

Install

How do I install the Last Frost Date and Hardiness Zone MCP server?

Last Frost Date and Hardiness Zone MCP is a hosted endpoint at https://last-frost-date-hardiness-zone-mcp.lipmichal.workers.dev/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 · last-frost-date-hardiness-zone-mcp.lipmichal.workers.dev

# add to Claude Code
claude mcp add --transport http theluckystrike-last-frost-date-hardiness-zone-mc 'https://last-frost-date-hardiness-zone-mcp.lipmichal.workers.dev/mcp'
Common questions

What is the Last Frost Date and Hardiness Zone MCP server?

Last Frost Date and Hardiness Zone MCP is listed in the public MCP registry as io.github.theluckystrike/last-frost-date-hardiness-zone-mcp. Last frost dates, USDA hardiness zone by ZIP, frost forecast and a vegetable planting calendar. This page covers its hosted endpoint (https://last-frost-date-hardiness-zone-mcp.lipmichal.workers.dev/mcp).

Is the Last Frost Date and Hardiness Zone MCP server safe to use?

Last Frost Date and Hardiness Zone MCP scores 67 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 Last Frost Date and Hardiness Zone MCP server expose?

Last Frost Date and Hardiness Zone MCP exposes 4 tools: hardiness_zone, frost_dates, frost_forecast, planting_calendar. Their descriptions and schemas cost roughly 699 tokens of context every time the server is loaded.

Does the Last Frost Date and Hardiness Zone MCP server require authentication?

No. We connected to Last Frost Date and Hardiness Zone MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Last Frost Date and Hardiness Zone MCP server still maintained?

Last Frost Date and Hardiness Zone MCP 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 Last Frost Date and Hardiness Zone MCP server?

VerifyMCP ran 12 checks on Last Frost Date and Hardiness Zone MCP, 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 Last Frost Date and Hardiness Zone MCP: 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.