Us Drought Monitor
NPM · @PIPEWORX/MCP-US-DROUGHT-MONITOR · 2 COMPONENTS
US Drought Monitor
Available components
Last scanned (3 hours ago)
Scores higher than 58% of npm servers
Category Maps and Location
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-us-drought-monitor). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-us-drought-monitor@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-us-drought-monitor |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-us-drought-monitor/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560844014 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c15b796be0e7a3e64e4368694a2bb3fe843886ed89d0c654604b6300b228bf68ecdfe3bca84c9f9c62562ead6203d36e434114342c0ebc3c6c6d2a35a |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
us_drought_county ~313
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
us_drought_national ~256
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
us_drought_state ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | State or territory name, two-letter postal abbreviation, or two-digit FIPS code, e.g. 'Texas', 'TX', or '48'. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-us-drought-monitor
claude mcp add pipeworx-io-us-drought-monitor -- npx -y @pipeworx/mcp-us-drought-monitor
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.