# USGS Water Services MCP Server (pypi · usgs-mcp)

USGS Water Services streamflow, flood stages, and peak events via waterservices.usgs.gov

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- pypi · `usgs-mcp`: 78/100 (this document), [markdown](https://verifymcp.io/servers/oceanmodeling-usgs-mcp/usgs-mcp.md), [page](https://verifymcp.io/servers/oceanmodeling-usgs-mcp/usgs-mcp)

## Channel facts

- Registry: `pypi`
- Package: `usgs-mcp`
- Version: `0.1.1`
- 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-10-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to oceanmodeling/ocean-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1761 tokens (~176/item across 10 items; 10 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**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 USGS Water Services MCP Server server?

USGS Water Services MCP Server runs locally as a PyPI package, launched with uvx usgs-mcp. 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 oceanmodeling-usgs-mcp -- uvx usgs-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "oceanmodeling-usgs-mcp": {
      "command": "uvx",
      "args": [
        "usgs-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "oceanmodeling-usgs-mcp": {
      "command": "uvx",
      "args": [
        "usgs-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add oceanmodeling-usgs-mcp -- uvx usgs-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "oceanmodeling-usgs-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "usgs-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add oceanmodeling-usgs-mcp --command uvx --arg usgs-mcp
```

### Hermes

```yaml
mcp_servers:
  oceanmodeling-usgs-mcp:
    command: "uvx"
    args: ["usgs-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "oceanmodeling-usgs-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "usgs-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add oceanmodeling-usgs-mcp -t stdio -c uvx -a usgs-mcp
```

### Other

```json
{
  "mcpServers": {
    "oceanmodeling-usgs-mcp": {
      "command": "uvx",
      "args": [
        "usgs-mcp"
      ]
    }
  }
}
```

## 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-02 (score 78, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-01 (score 63)

First indexed and scored.

## MCP tools (10)

### `usgs_get_peak_streamflow` (~146 tokens)

Get annual peak streamflow records for a USGS site.

Returns the highest flow recorded each year, including discharge and
gage height. Many sites have 50+ years of record. Useful for flood
frequency analysis and understanding historical flood severity.

Args:
    site_number: 8-digit USGS site number (e.g., '01646500').
    start_year: Optional start year filter.
    end_year: Optional end year filter.
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `end_year`
- `response_format` (string)
- `site_number` (string, required)
- `start_year`

Output parameters:

- `result` (string)

### `usgs_get_flood_status` (~106 tokens)

Assess current flood conditions at a USGS site.

Combines current instantaneous data with peak flow history and
statistical context to determine whether conditions are normal,
above normal, or at flood stage.

Args:
    site_number: 8-digit USGS site number (e.g., '01646500').
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `response_format` (string)
- `site_number` (string, required)

Output parameters:

- `result` (string)

### `usgs_find_sites` (~226 tokens)

Find USGS gauge stations by state or bounding box.

Search for active USGS streamflow monitoring sites. Returns site ID, name,
coordinates, and drainage area.

Args:
    state_code: US state 2-letter code (e.g., 'MD', 'TX'). Either state_code or bbox required.
    bbox: Bounding box as 'west,south,east,north' decimal degrees. Either state_code or bbox required.
    site_type: Site type code — 'ST' (stream, default), 'LK' (lake), 'SP' (spring).
    parameter_code: USGS parameter code — '00060' (discharge, default) or '00065' (gage height).
    limit: Maximum number of sites to return (default 20).
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `bbox`
- `limit` (integer)
- `parameter_code` (string)
- `response_format` (string)
- `site_type` (string)
- `state_code`

Output parameters:

- `result` (string)

### `usgs_get_site_info` (~103 tokens)

Get detailed metadata for a specific USGS site.

Returns full site details including name, coordinates, county, HUC code,
drainage area, datum, and contributing drainage area.

Args:
    site_number: 8-digit USGS site number (e.g., '01646500').
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `response_format` (string)
- `site_number` (string, required)

Output parameters:

- `result` (string)

### `usgs_find_nearest_sites` (~198 tokens)

Find USGS sites near a geographic point.

Searches for active streamflow sites within a radius of the given
coordinates, sorted by distance.

Args:
    latitude: Latitude in decimal degrees.
    longitude: Longitude in decimal degrees.
    radius_miles: Search radius in miles (default 25).
    parameter_code: USGS parameter code — '00060' (discharge, default) or '00065' (gage height).
    limit: Maximum number of sites to return (default 10).
    response_format: Output format — 'markdown' (default), 'json', or
        'geojson' (a FeatureCollection of Point features, [lon, lat]).

Input parameters:

- `latitude` (number, required)
- `limit` (integer)
- `longitude` (number, required)
- `parameter_code` (string)
- `radius_miles` (number)
- `response_format` (string)

Output parameters:

- `result` (string)

### `usgs_get_monthly_stats` (~150 tokens)

Get monthly streamflow statistics for a USGS site.

Returns long-term monthly statistics including mean, min, max, and
percentiles (P10, P25, P50, P75, P90) for each month. Useful for
understanding seasonal flow patterns.

Args:
    site_number: 8-digit USGS site number (e.g., '01646500').
    parameter_code: USGS parameter code — '00060' (discharge, default).
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `parameter_code` (string)
- `response_format` (string)
- `site_number` (string, required)

Output parameters:

- `result` (string)

### `usgs_get_daily_stats` (~166 tokens)

Get daily streamflow statistics (flow duration) for a USGS site.

Returns percentiles showing the typical flow range for each day of the
year based on the complete period of record. Useful for understanding
whether current conditions are normal for the time of year.

Args:
    site_number: 8-digit USGS site number (e.g., '01646500').
    parameter_code: USGS parameter code — '00060' (discharge, default).
    month: Optional month number (1-12) to filter results.
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `month`
- `parameter_code` (string)
- `response_format` (string)
- `site_number` (string, required)

Output parameters:

- `result` (string)

### `usgs_get_instantaneous_values` (~239 tokens)

Get real-time (instantaneous) streamflow data from a USGS site.

Returns ~15-minute interval data for up to the last 120 days.
Common use: checking current river conditions and recent trends.

Args:
    site_number: 8-digit USGS site number (e.g., '01646500').
    parameter_code: USGS parameter code — '00060' (discharge, default) or '00065' (gage height).
    period: ISO 8601 duration for lookback period (default 'P7D' = 7 days). Max 'P120D'.
    response_format: Output format — 'markdown' (default) or 'json'.
    max_points: For json output, cap each series to the most recent N points
        (default 2000) so a long period doesn't flood context; the response
        carries a {truncated,returned,total} envelope.

Input parameters:

- `max_points` (integer)
- `parameter_code` (string)
- `period` (string)
- `response_format` (string)
- `site_number` (string, required)

Output parameters:

- `result` (string)

### `usgs_get_daily_values` (~271 tokens)

Get daily mean/min/max streamflow values from a USGS site.

Returns daily statistical values over a date range. Decades of historical
data are available at most sites.

Args:
    site_number: 8-digit USGS site number (e.g., '01646500').
    start_date: Start date as YYYY-MM-DD.
    end_date: End date as YYYY-MM-DD.
    parameter_code: USGS parameter code — '00060' (discharge, default) or '00065' (gage height).
    stat_code: Statistic code — '00003' (mean, default), '00001' (max), '00002' (min).
    response_format: Output format — 'markdown' (default) or 'json'.
    max_points: For json output, cap each series to the most recent N points
        (default 2000) so a multi-decade range doesn't flood context; the
        response carries a {truncated,returned,total} envelope.

Input parameters:

- `end_date` (string, required)
- `max_points` (integer)
- `parameter_code` (string)
- `response_format` (string)
- `site_number` (string, required)
- `start_date` (string, required)
- `stat_code` (string)

Output parameters:

- `result` (string)

### `usgs_get_hydrograph` (~156 tokens)

Get streamflow data formatted for hydrograph context.

Fetches recent instantaneous values and optionally compares them to
historical daily median statistics for context. Useful for understanding
whether current conditions are above or below normal.

Args:
    site_number: 8-digit USGS site number (e.g., '01646500').
    days: Number of days of recent data (default 7, max 120).
    include_median: Include historical median comparison (default True).
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `days` (integer)
- `include_median` (boolean)
- `response_format` (string)
- `site_number` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/oceanmodeling-usgs-mcp/usgs-mcp#diagnostics

## Score history

- 2026-10-04: 78
- 2026-10-03: 78
- 2026-10-02: 78
- 2026-10-01: 63

## Common questions

### What is the USGS Water Services MCP Server server?

USGS Water Services MCP Server is listed in the public MCP registry as io.github.oceanmodeling/usgs-mcp. USGS Water Services streamflow, flood stages, and peak events via waterservices.usgs.gov. This page covers its PyPI package (usgs-mcp).

### Is the USGS Water Services MCP Server server safe to use?

USGS Water Services MCP Server scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. 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 USGS Water Services MCP Server server expose?

USGS Water Services MCP Server exposes 10 tools: usgs_get_peak_streamflow, usgs_get_flood_status, usgs_find_sites, usgs_get_site_info, usgs_find_nearest_sites, and 5 more. Their descriptions and schemas cost roughly 1,761 tokens of context every time the server is loaded.

### Is the USGS Water Services MCP Server server still maintained?

USGS Water Services MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 October 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 USGS Water Services MCP Server server under?

USGS Water Services MCP Server 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

- PyPI project: https://pypi.org/project/usgs-mcp/
- Socket report: https://socket.dev/pypi/package/usgs-mcp
- Repository: https://github.com/oceanmodeling/ocean-mcp
- Changelog RSS feed: https://verifymcp.io/servers/oceanmodeling-usgs-mcp/usgs-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/oceanmodeling-usgs-mcp/usgs-mcp.json
- HTML version of this page: https://verifymcp.io/servers/oceanmodeling-usgs-mcp/usgs-mcp