MCP.Market

US Drought Monitor MCP server

online · 100% uptime
by olyport.com·com.olyport/drought·v1.1.0

Current drought conditions and severity across the United States

C69/100grade C
What users say
No reviews yet
Be the first
Safety scan
C69/100

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed US Drought Monitor yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

US Drought Monitor tools (3)

write = sends, deletes, buys or posts
  • get_current_droughtFree

    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).

  • get_drought_historyFree

    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_summaryFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

1 low
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 56ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenanceno repository listed3/15
  • Maintainer identityverified namespace with website, no repo4/10

Findings (1)

  • lowNo source repository listedmaint.no-repo
Overall 69/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How US Drought Monitor compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
69/100
higher than 32% of 48,243 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
103 ms
faster than 83% of 30,027 servers

What its tools let an agent do: 3 read

Install US Drought Monitor in Claude Code, Cursor or VS Code

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

US Drought Monitor: common questions

Is US Drought Monitor MCP server safe?
With care: it is graded C, so read the findings first (69/100). Read the US Drought Monitor safety report
How do I install US Drought Monitor?
It runs remotely at mcp.olyport.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does US Drought Monitor need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is US Drought Monitor maintained?
The latest release is v1.1.0.
Is US Drought Monitor up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does US Drought Monitor compare with other MCP servers?
safety score 69/100 (higher than 32% of 48,243 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from olyport.com →