Remote MCP server that returns published U.S. weather records for a street address and date, plus county storm history and NWS forecasts.
What you can do
Submit a weather-records lookup for one U.S. street address and date, then poll it until done or failed
Read finished lookup results with their provenance and notice, or the failure reason
Retrieve hail, thunderstorm wind and tornado events of record for a published U.S. county over about three years
Get the current National Weather Service forecast for a U.S. point or address, with 12-hour periods and hourly values
When to use it
Useful when an assistant needs documented, sourced weather history for a specific U.S. address and date, or a quick county-level storm record or NWS forecast, rather than general climate commentary.
Requirements
Remote streamable HTTP endpoint; no local install. Lookups and address-based forecasts need a free key (10 lookups a month) sent as an Authorization: Bearer header. County storm history and latitude/longitude forecasts work without a key. Lookups take about two minutes to complete.
Before you install
The Authorization header carries a secret API key; keep it out of logs and shared transcripts. Each accepted lookup consumes the monthly quota. Results are records, not determinations about a property, and a missing record is not proof an event did not occur. Forecasts are not observed records.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.weatherofrecord%2Fweather-of-record/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametersdaterequiredaddressrequired
get_lookup
Get a lookup's status and records
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.
Parameterslookup_idrequired
get_county_storm_history
Get a county's storm history
Returns the hail, thunderstorm wind and tornado events of record for one published U.S. county over about the last three years, from NOAA's Storm Events Database, with the source file and revision named. Needs no key. state is the two-letter abbreviation and county is written as in the county page address, for example tn and sumner. The list of published counties is at https://weatherofrecord.com/api/v1/storms. County level only, never a street address. The absence of a record is not evidence that an event did not occur.
Parametersstaterequiredcountyrequired
get_forecast
Get the current National Weather Service forecast
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.
Parametershoursaddressperiodslatitudelongitude
Version history
2
v1.1.0LatestOct 29, 2026
v1.0.0Sep 30, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.