US Drought Monitor MCP Server

com.olyport/drought

answering

US Drought Monitor is answering right now. Last checked 12 min ago. It exposes 3 tools.

Current drought conditions and severity across the United States

Uptime history 40 hours of history

40 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

552 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add drought --transport http https://mcp.olyport.com/drought/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "drought": {
      "url": "https://mcp.olyport.com/drought/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.drought]
url = "https://mcp.olyport.com/drought/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "drought": {
      "url": "https://mcp.olyport.com/drought/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "drought": {
      "url": "https://mcp.olyport.com/drought/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

drought

get_drought_history

Get historical drought conditions over time from the US Drought Monitor. Returns weekly drought severity percentages for the specified area and date range. The Drought Monitor is updated every Tuesday, so data points are weekly. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). county_fips: Five-digit county FIPS code (e.g. '06037' for Los Angeles County). start_date: Start date in YYYY-MM-DD format. Defaults to one year ago. end_date: End date in YYYY-MM-DD format. Defaults to today.

get_drought_summary

Get a national drought summary with total affected area percentages. Returns the current national overview showing what percentage of the US is experiencing each drought level (D0 through D4), plus the total area affected by any drought condition. Useful for getting a quick picture of drought conditions across the entire country.

current

get_current_drought

Get current drought conditions from the US Drought Monitor. Returns the percentage of area at each drought intensity level: - None: No drought - D0: Abnormally Dry - D1: Moderate Drought - D2: Severe Drought - D3: Extreme Drought - D4: Exceptional Drought Provide either a state abbreviation for statewide data or a county FIPS code for county-level detail. Omit both for national data. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). county_fips: Five-digit county FIPS code (e.g. '06037' for Los Angeles County).

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.olyport.com/drought/mcp	streamable-http	answering	614 ms	12 min ago

US Drought Monitor — questions

Answers built from our own checks of this server.

What can US Drought Monitor do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_current_drought, get_drought_history, get_drought_summary. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is US Drought Monitor working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 552 ms. The bar chart above shows every period we have measured.

How do I connect US Drought Monitor?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does US Drought Monitor need an API key?

No. US Drought Monitor completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is US Drought Monitor?

It answers our handshake in 552 ms on average, which is faster than 19% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.