US Drought Monitor MCP Server

by olyport Your server? Claim it

answering

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

Current drought conditions and severity across the United States

Uptime history 91 days of history

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

530 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check US Drought Monitor every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 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

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "drought": {
      "type": "http",
      "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	531 ms	13 min ago

Alternatives to US Drought Monitor

same job, measured the same way

Drought MCP

by mrfentmen

US Drought Monitor statistics: drought severity shares by state, weekly, straight from the USDM API

642 installs/wk local only

Us Drought Monitor MCP Server

by cyanheads

Query U.S. Drought Monitor severity, DSCI, population, and drought duration.

529 installs/wk 7 tools answering

Us Drought Monitor

by pipeworx-io

US Drought Monitor

265 installs/wk 47 tools answering

ZennoDroid: tasks

by zennolab

Create, configure, start and monitor ZennoDroid tasks and their sessions.

local only

ZennoPoster: tasks

by zennolab

Create, configure, start and monitor ZennoPoster tasks and their sessions.

local only

BountyHunte.rs

by bountyhunte

Search and monitor bug bounty programs and audit contests across ten platforms.

answering

Rewst MCP

by servosity

Operate and monitor Rewst RPA across every client org: automation health, failures, ROI, and drift.

local only

Trustmodel MCP

by karlmehta

Score any AI for trust across 10 dimensions; evaluate, monitor & govern LLMs and agents.

155 installs/wk local only

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 530 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 in the form 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 530 ms on average, which is faster than 23% 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.