A
licenseB
qualityD
maintenanceA Model Context Protocol server that provides tools to fetch weather alerts for US states and forecasts based on latitude/longitude coordinates using the US National Weather Service API.
2
95 npm
1
MIT
mcp-usa-climate-risk
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-usa-climate-riskWhat's the climate risk for ZIP 10001?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-usa-climate-risk
Model Context Protocol server for real-time US climate risk and home insurance metrics.
Overview
mcp-usa-climate-risk is an open-source Model Context Protocol server that exposes real-time US climate risk data to LLM agents. It provides a single, robust tool — get_zip_climate_risk — that queries the RiskBeforeBuy API to return parcel-level hazard scores, estimated homeowners insurance premiums, premium-to-income strain, and state insurance market pressure for any valid 5-digit US ZIP code.
Built for Claude Desktop, Cursor IDE, Windsurf, and any MCP-compatible AI environment.
Related MCP server: Weather MCP Server
Installation
Prerequisites
Node.js >= 18.0.0
npm or pnpm
A supported MCP client (Claude Desktop, Cursor, Windsurf)
Clone & Build
git clone https://github.com/opendata-collective/mcp-usa-climate-risk.git
cd mcp-usa-climate-risk
npm install
npm run buildClient Configuration
Claude Desktop
Add the following to your Claude Desktop MCP configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"usa-climate-risk": {
"command": "node",
"args": ["/absolute/path/to/mcp-usa-climate-risk/dist/index.js"]
}
}
}After restarting Claude Desktop, the get_zip_climate_risk tool will appear in your available tools.
Cursor IDE
Add the following to your Cursor MCP configuration (.cursor/mcp.json in your project root, or the global settings):
{
"mcpServers": {
"usa-climate-risk": {
"command": "node",
"args": ["/absolute/path/to/mcp-usa-climate-risk/dist/index.js"]
}
}
}Windsurf
Add the following to your Windsurf MCP configuration:
{
"mcpServers": {
"usa-climate-risk": {
"command": "node",
"args": ["/absolute/path/to/mcp-usa-climate-risk/dist/index.js"]
}
}
}Development Mode
To run the server in development mode with hot-reloading via tsx:
npm run devTool Reference
get_zip_climate_risk
Fetches comprehensive climate hazards, estimated home insurance premiums, premium-to-income strain, and market carrier pressure metrics for any valid 5-digit US ZIP Code.
Parameters:
Name | Type | Required | Description |
|
| Yes | 5-digit US ZIP code (regex: |
Response (HTTP 200):
Returns a formatted Markdown summary:
## Climate Risk Report — ZIP 28801
| Metric | Value |
|--------|-------|
| **Overall Risk** | high |
| **Est. Annual Premium** | $2,287 – $4,130 / year |
| **Premium Strain** | high |
| **Market Pressure** | high |
_Source: Risk Before Buy — Federal data (FEMA, NOAA, USGS, USDA, EPA)._Error Responses:
Status | Meaning | Message |
404 | ZIP not found | "ZIP code not found in our climate registry." |
429 | Rate limited | "Rate limit exceeded for the public tier (5 req/min)..." |
Network error | Connection failure | Graceful error message, never crashes |
Data Sources
All risk metrics are derived from verified federal datasets:
Agency | Dataset | Coverage |
FEMA | National Risk Index (NRI) | Flood, hurricane, wildfire, earthquake |
NOAA | Storm Events Database | Historical severe weather claims |
USGS | Earthquake Hazards Program | Seismic peak ground acceleration |
USDA | Forest Service Wildfire Risk | Wildfire probability to communities |
EPA | Climate Exposure Overlays | Environmental hazard proximity |
Powered by the RiskBeforeBuy Official Platform.
API Rate Limits
The public tier allows 5 requests per minute per IP. For bulk lookups and production integrations, consult the RiskBeforeBuy API Documentation.
Contributing
Contributions are welcome from data engineers, climate scientists, and MCP ecosystem developers. Areas of interest:
Additional MCP tools (e.g., parcel-level flood zone lookup, insurance market deep-dive)
Alternative transport implementations (Streamable HTTP, SSE)
Client SDK wrappers for Python, Go, Rust
Test coverage and data validation scripts
Please open an issue or submit a pull request.
License
MIT — Open Data Collective © 2026
Available Tools
1 toolget_zip_climate_riskA
Fetches comprehensive climate hazards, estimated home insurance premiums, premium-to-income strain, and market carrier pressure metrics for any valid 5-digit US ZIP Code. Use this tool whenever a user asks about real estate due diligence, moving to a new area, property risk profiles, or homeownership costs in a specific location.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| zip | Yes | 5-digit US ZIP code to look up |
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions the data fetched (climate hazards, premiums, etc.), which implies a read-only operation, but does not explicitly state side effects, authentication requirements, or rate limits. For a data retrieval tool, this is adequate but could be more transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. First sentence defines the function, second provides usage guidance. Front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a single parameter and no output schema, the description is fairly complete. It explains what the tool does and when to use it. It does not describe the output structure, but for a simple retrieval tool, the user might infer from the described metrics. Could be improved by mentioning typical output format.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage for the single parameter (zip), including pattern and required status. The description does not add additional meaning beyond what the schema provides; it merely restates 'any valid 5-digit US ZIP Code.' Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches comprehensive climate hazards, insurance premiums, and related metrics for any valid 5-digit US ZIP code. The verb 'fetches' and resource 'climate risk data for ZIP code' are specific. No sibling tools exist, so no differentiation needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states: 'Use this tool whenever a user asks about real estate due diligence, moving to a new area, property risk profiles, or homeownership costs in a specific location.' This provides clear context for when to use it. No alternatives are mentioned due to lack of sibling tools, but the guidance is direct and helpful.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
get_zip_climate_risk
TDQS
A4.1/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no risk of confusion between tools. The tool's purpose is clearly distinct.
Naming Consistency5/5
The single tool uses a clear 'verb_noun' pattern (get_zip_climate_risk), consistent and readable.
Tool Count3/5
One tool is on the lower end of the range, but it covers a specific, narrow domain. It is borderline but not too few given the focused purpose.
Completeness4/5
The tool comprehensively addresses climate risk data for a zip code, but lacks additional operations like comparison or metadata retrieval, which are minor gaps.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
Remote MCP endpoint for U.S. home forecasts, public benchmark data, and permit or zoning readiness.
Geospatial AI MCP server — satellite imagery, embeddings, weather, GNS governance
The official Model Context Protocol server for Ambee. It gives any MCP-compatible AI assistant — Claude, ChatGPT, Cursor, VS Code, Ollama, and more direct access to live air quality, pollen, and weather data. To get started, including information on signing up and obtaining your Ambee key, check out the Ambee documentation on https://docs.ambeedata.com
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models to fetch weather alerts and detailed forecasts for US locations using the National Weather Service API.95 npmGPL 3.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server providing seamless access to the Hawaii Climate Data Portal API for querying climate and weather data for Hawaii and American Samoa.-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides real-time weather alerts and forecasts using the National Weather Service API.-