Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.andrewschristison/pondlog-usgs

NPM · @PONDLOG/MCP-USGS · SCANNED SEP 22

USGS Water Services MCP server. Real-time streamflow, gage height, and site metadata from NWIS.

Available components

0 this week 83 Trust /100
Trust breakdown (7 categories)

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 Security98
  • 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
  • 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1003 tokens (~250/item across 4 items; 4 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 4 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
Install

How do I install the io.github.andrewschristison/pondlog-usgs MCP server?

io.github.andrewschristison/pondlog-usgs runs locally as an npm package, launched with npx -y @pondlog/mcp-usgs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pondlog/mcp-usgs

# add to Claude Code
claude mcp add andrewschristison-pondlog-usgs -- npx -y @pondlog/mcp-usgs
// .cursor/mcp.json
{
  "mcpServers": {
    "andrewschristison-pondlog-usgs": {
      "command": "npx",
      "args": [
        "-y",
        "@pondlog/mcp-usgs"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "andrewschristison-pondlog-usgs": {
      "command": "npx",
      "args": [
        "-y",
        "@pondlog/mcp-usgs"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add andrewschristison-pondlog-usgs -- npx -y @pondlog/mcp-usgs
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "andrewschristison-pondlog-usgs": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pondlog/mcp-usgs"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add andrewschristison-pondlog-usgs --command npx --arg -y --arg @pondlog/mcp-usgs
# ~/.hermes/config.yaml
mcp_servers:
  andrewschristison-pondlog-usgs:
    command: "npx"
    args: ["-y", "@pondlog/mcp-usgs"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "andrewschristison-pondlog-usgs": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pondlog/mcp-usgs"
      ]
    }
  }
}
# add to Vellum
assistant mcp add andrewschristison-pondlog-usgs -t stdio -c npx -a -y @pondlog/mcp-usgs
// mcp.json
{
  "mcpServers": {
    "andrewschristison-pondlog-usgs": {
      "command": "npx",
      "args": [
        "-y",
        "@pondlog/mcp-usgs"
      ]
    }
  }
}
Changelog

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.

  • 22 Sept 26 0
    • Stability: 0.97 → pass security
  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 22 Sept 2026 · Analysed npm/@pondlog/mcp-usgs@0.1.6

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 98 packages
Packages resolved 98
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~1,003 tokens

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 →

Tool Tokens
get_daily_values ~278

Daily statistics (default: mean) for one or more USGS gauges. Use this for any query that crosses days or asks about historic dates. Pass either `period` (relative-to-now) OR `start_date`/`end_date` (historic range), not both. For real-time sub-hour resolution prefer `get_instantaneous_values`. Returns one daily value per (site × parameter × statistic × day). USGS quality codes: 'A' = approved, 'P' = provisional.

NameTypeReqDescription
end_dateHistoric range end (YYYY-MM-DD). Defaults to today when start_date is set.
parameter_codesarray5-digit parameter codes. Defaults to ['00060'] (discharge mean).
periodstringRelative window ending now. Examples: 'P7D', 'P30D', 'P1Y'. Mutually exclusive with start_date/end_date.
sitesarrayyesArray of USGS site numbers. Single-site queries are typical.
start_datestringHistoric range start (YYYY-MM-DD). Pair with end_date for an explicit window.
statistic_codesarrayUSGS statistic codes, '00003' = mean (default), '00001' = max, '00002' = min, '00008' = median.

No output schema declared.

No examples provided.

get_instantaneous_values ~241

Real-time readings (typically 15-minute cadence) from a USGS gauge. Returns one or more time series, by default discharge (00060, ft³/s) and gage height (00065, ft), over a relative period ending now. Use this to answer 'what is the river doing right now?'. USGS rejects historic dates on this endpoint; for past data use `get_daily_values` with start_date/end_date instead. For a 'what gauges exist near here?' first-step query use `search_sites`.

NameTypeReqDescription
parameter_codesarraySpecific 5-digit parameter codes to retrieve. Defaults to ['00060', '00065'] (discharge + gage height). Pass ['00010'] for water temperature, etc.
periodstringRelative time window ending now. Default 'PT2H' (past 2 hours, returns ~8 readings at 15-minute cadence). 'P1D' returns ~96 readings.
sitesarrayyesArray of USGS site numbers to fetch in one call. Most queries pass a single site, but the API supports batched fetches.

No output schema declared.

No examples provided.

get_site_info ~150

Returns metadata for a single USGS gauging station: official name, coordinates, site type (stream/lake/groundwater/etc.), hydrologic unit (HUC), state/county codes, and gauge altitude. Use after `search_sites` finds candidate gauges, or to confirm a site number returned in someone's data.

NameTypeReqDescription
site_numberstringyesUSGS site number, 8 to 15 digits identifying a single gauging station. Examples: '12045500' (Elwha River at McDonald Bridge near Port Angeles, WA); '12048000' (Dungeness River near Sequim, WA). Use `…

No output schema declared.

No examples provided.

search_sites ~334

Find active USGS stream-gauge sites by either (a) latitude/longitude/radius_km, or (b) US state postal code. Returns site numbers, names, coordinates, HUC, and altitude, feed the resulting site numbers into `get_instantaneous_values` or `get_daily_values`. Defaults filter to surface-water streams (siteType=ST) with real-time data (hasDataTypeCd=iv); pass site_type/has_data_type to override. Pass either lat+lng+radius_km OR state_code; the lat/lng path is preferred for place-aware queries.

NameTypeReqDescription
has_data_typestringRestrict to sites that publish the given data type: 'iv' = instantaneous (real-time, default), 'dv' = daily values, 'qw' = water quality, 'gw' = groundwater levels.
latnumberLatitude of the search center. Required if state_code is not provided.
lngnumberLongitude of the search center. Required if state_code is not provided.
radius_kmnumberSearch radius in km around (lat, lng). Default 25.
site_typestringUSGS site type code: 'ST' = stream (default), 'LK' = lake, 'GW' = groundwater, 'AT' = atmosphere, 'ES' = estuary. Full list: https://help.waterdata.usgs.gov/site_tp_cd
state_codestringUS two-letter state code. Mutually exclusive with lat/lng. Returns ALL active stream gauges in the state.

No output schema declared.

No examples provided.

Common questions

What is the io.github.andrewschristison/pondlog-usgs MCP server?

io.github.andrewschristison/pondlog-usgs is an MCP server listed in the public MCP registry as io.github.andrewschristison/pondlog-usgs. USGS Water Services MCP server. Real-time streamflow, gage height, and site metadata from NWIS. This page covers its npm package (@pondlog/mcp-usgs).

Is the io.github.andrewschristison/pondlog-usgs MCP server safe to use?

io.github.andrewschristison/pondlog-usgs scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 io.github.andrewschristison/pondlog-usgs MCP server expose?

io.github.andrewschristison/pondlog-usgs exposes 4 tools: get_instantaneous_values, get_daily_values, get_site_info, search_sites. Their descriptions and schemas cost roughly 1,003 tokens of context every time the server is loaded.

Is the io.github.andrewschristison/pondlog-usgs MCP server still maintained?

io.github.andrewschristison/pondlog-usgs is still listed as active in the MCP registry. We last reached this channel on 22 September 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 io.github.andrewschristison/pondlog-usgs MCP server under?

io.github.andrewschristison/pondlog-usgs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.