# Us Drought Monitor (npm · @pipeworx/mcp-us-drought-monitor)

US Drought Monitor

- Trust score: 78/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-us-drought-monitor/us-drought-monitor-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-us-drought-monitor/us-drought-monitor-mcp)
- npm · `@pipeworx/mcp-us-drought-monitor`: 78/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-us-drought-monitor/pipeworx-mcp-us-drought-monitor.md), [page](https://verifymcp.io/servers/pipeworx-io-us-drought-monitor/pipeworx-mcp-us-drought-monitor)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-us-drought-monitor`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-us-drought-monitor).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 842 tokens (~280/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Us Drought Monitor MCP server?

Us Drought Monitor runs locally as an npm package, launched with npx -y @pipeworx/mcp-us-drought-monitor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-us-drought-monitor -- npx -y @pipeworx/mcp-us-drought-monitor
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-us-drought-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-us-drought-monitor"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-us-drought-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-us-drought-monitor"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-us-drought-monitor -- npx -y @pipeworx/mcp-us-drought-monitor
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-us-drought-monitor": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-us-drought-monitor"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-us-drought-monitor --command npx --arg -y --arg @pipeworx/mcp-us-drought-monitor
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-us-drought-monitor:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-us-drought-monitor"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-us-drought-monitor": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-us-drought-monitor"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-us-drought-monitor -t stdio -c npx -a -y @pipeworx/mcp-us-drought-monitor
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-us-drought-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-us-drought-monitor"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `us_drought_national` (~256 tokens)

Weekly U.S. Drought Monitor drought-severity statistics for the nation: percent of area or percent of population in categories None, D0 (abnormally dry) through D4 (exceptional drought). Categories are cumulative (D1+ means D1 through D4 combined, i.e. 'at least moderate drought'). Covers the contiguous 48 states (conus), the contiguous states plus Alaska/Hawaii/Puerto Rico (total), or both at once (us). Published weekly — map valid every Tuesday, released the following Thursday. Omit dates for the latest available map.

Input parameters:

- `area` (string): conus = contiguous 48 states only. total = contiguous states plus Alaska, Hawaii, and Puerto Rico. us = both rows at once. Default conus.
- `end_date` (string): Latest map date, YYYY-MM-DD or M/D/YYYY. Omit for the latest single map.
- `measure` (string): 'area' = percent of land area in each category (default). 'population' = percent of the area's population in each category.
- `start_date` (string): Earliest map date, YYYY-MM-DD or M/D/YYYY. Omit for the latest single map.

### `us_drought_state` (~217 tokens)

Weekly U.S. Drought Monitor drought-severity statistics for one U.S. state or territory: percent of area or percent of population in categories None, D0 (abnormally dry) through D4 (exceptional drought). Categories are cumulative (D1+ means D1 through D4 combined). Published weekly — map valid every Tuesday, released the following Thursday. Omit dates for the latest available map.

Input parameters:

- `end_date` (string): Latest map date, YYYY-MM-DD or M/D/YYYY. Omit for the latest single map.
- `measure` (string): 'area' = percent of land area in each category (default). 'population' = percent of the state's population in each category.
- `start_date` (string): Earliest map date, YYYY-MM-DD or M/D/YYYY. Omit for the latest single map.
- `state` (string, required): State or territory name, two-letter postal abbreviation, or two-digit FIPS code, e.g. 'Texas', 'TX', or '48'.

### `us_drought_county` (~313 tokens)

Weekly U.S. Drought Monitor drought-severity statistics for one U.S. county: percent of county area or percent of county population in categories None, D0 (abnormally dry) through D4 (exceptional drought). Categories are cumulative (D1+ means D1 through D4 combined). Published weekly — map valid every Tuesday, released the following Thursday. Match by state plus county name (e.g. state 'TX', county 'Travis'), or pass the county's 5-digit FIPS code directly. Omit dates for the latest available map.

Input parameters:

- `county` (string): County name, with or without the word 'County' (e.g. 'Travis' or 'Travis County'). Required unless fips is given.
- `end_date` (string): Latest map date, YYYY-MM-DD or M/D/YYYY. Omit for the latest single map.
- `fips` (string): The county's 5-digit FIPS code. Use instead of state+county when known.
- `measure` (string): 'area' = percent of the county's land area in each category (default). 'population' = percent of the county's population in each category.
- `start_date` (string): Earliest map date, YYYY-MM-DD or M/D/YYYY. Omit for the latest single map.
- `state` (string): State name or two-letter postal abbreviation, e.g. 'Texas' or 'TX'. Required unless fips is given.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-us-drought-monitor/pipeworx-mcp-us-drought-monitor#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Us Drought Monitor MCP server?

Us Drought Monitor is an MCP server listed in the public MCP registry as io.github.pipeworx-io/us-drought-monitor. US Drought Monitor. This page covers its npm package (@pipeworx/mcp-us-drought-monitor).

### Is the Us Drought Monitor MCP server safe to use?

Us Drought Monitor scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Us Drought Monitor MCP server expose?

Us Drought Monitor exposes 3 tools: us_drought_national, us_drought_state, us_drought_county. Their descriptions and schemas cost roughly 786 tokens of context every time the server is loaded.

### Is the Us Drought Monitor MCP server still maintained?

Us Drought Monitor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Us Drought Monitor MCP server under?

Us Drought Monitor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-us-drought-monitor
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-us-drought-monitor
- Repository: https://github.com/pipeworx-io/mcp-us-drought-monitor
- Website: https://pipeworx.io/packs/us-drought-monitor
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-us-drought-monitor/pipeworx-mcp-us-drought-monitor.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-us-drought-monitor/pipeworx-mcp-us-drought-monitor.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-us-drought-monitor/pipeworx-mcp-us-drought-monitor