Weather of Record
REMOTE · WEATHEROFRECORD.COM
Published weather records for a U.S. street address and date, with provenance.
Available components
Last scanned (18 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Maps and Location
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 548 tokens (~182/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 Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 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.
- 12 Oct 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.
- 11 Oct 26 0
- Server version: a393190 → 0170b67 functional
- 10 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 100% → 75% ▼ functional
- Schema quality: 355 → 548 ▼ functional
- Server version: 0c4f1f0 → a393190 functional
- New tool “get_forecast” 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 23 Oct 2026 · Probed https://weatherofrecord.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=weatherofrecord.com | CN=YE1,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 659c66873280a43fef1e23cb5198d9ff458 |
| SANs: weatherofrecord.com, weatheronrecord.com, www.weatherofrecord.com, www.weatheronrecord.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of weatherofrecord.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| weatherofrecord.com. | absent | 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 |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://weatherofrecord.com/mcp | Verified | 200 | |
| http (plaintext) | http://weatherofrecord.com/mcp | HTTPS enforced | 301 | https://weatherofrecord.com/mcp |
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_forecast Get the current National Weather Service forecast ~160
Returns the current National Weather Service forecast for a US point. This is a forecast, not a record of observed weather. Send latitude and longitude (no key needed), or a U.S. street address (needs the free key). Returns 12-hour periods for about seven days and hourly values, with issued_utc, the time the National Weather Service issued it, and a stale flag. U.S. coverage only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Full U.S. street address with city, state and ZIP (needs the free key) |
| hours | integer | – | Hourly values to return |
| latitude | number | – | – |
| longitude | number | – | – |
| periods | integer | – | 12-hour periods to return |
No output schema declared.
No examples provided.
get_lookup Get a lookup's status and records ~94
Check a lookup started with submit_lookup. The status is queued, running, done or failed. When done, the result holds the records with their provenance and a notice. A failed lookup carries a reason and no records. The absence of a record is not evidence that an event did not occur. Results are kept for 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| lookup_id | string | yes | The lookup_id from submit_lookup |
No output schema declared.
No examples provided.
submit_lookup Submit a weather-records lookup ~137
Start a weather-records lookup for one U.S. street address and date. Returns a lookup_id; the records are ready in about two minutes -- call get_lookup with it. Records reach back to about 1960. Records, not opinions: nothing returned is a determination about any property. Each accepted lookup uses one of the key's 10 free lookups this month.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Full U.S. street address with city, state and ZIP, e.g. 123 Main St, Nashville, TN 37203 |
| date | string | yes | The date of interest, YYYY-MM-DD |
No output schema declared.
No examples provided.
How do I install the Weather of Record MCP server?
Weather of Record is a hosted endpoint at https://weatherofrecord.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 · weatherofrecord.com
claude mcp add --transport http com-weatherofrecord-weather-of-record 'https://weatherofrecord.com/mcp'
What is the Weather of Record MCP server?
Weather of Record is an MCP server listed in the public MCP registry as com.weatherofrecord/weather-of-record. Published weather records for a U.S. street address and date, with provenance. This page covers its hosted endpoint (https://weatherofrecord.com/mcp).
Is the Weather of Record MCP server safe to use?
Weather of Record scores 74 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 Weather of Record MCP server expose?
Weather of Record exposes 3 tools: submit_lookup, get_lookup, get_forecast. Their descriptions and schemas cost roughly 391 tokens of context every time the server is loaded.
Does the Weather of Record MCP server require authentication?
No. We connected to Weather of Record without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Weather of Record MCP server still maintained?
Weather of Record is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.