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.

NOAA NDBC MCP Server

PYPI · NDBC-MCP · SCANNED SEP 20

NOAA National Data Buoy Center observations: waves, SST, wind, pressure from 1,300+ stations

Available components

−15 this week 56 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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency10
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1118 tokens (~139/item across 8 items; 8 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 Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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 NOAA NDBC MCP Server server?

NOAA NDBC MCP Server runs locally as a PyPI package, launched with uvx ndbc-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · ndbc-mcp

# add to Claude Code
claude mcp add mansurjisan-ndbc-mcp -- uvx ndbc-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "mansurjisan-ndbc-mcp": {
      "command": "uvx",
      "args": [
        "ndbc-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mansurjisan-ndbc-mcp": {
      "command": "uvx",
      "args": [
        "ndbc-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mansurjisan-ndbc-mcp -- uvx ndbc-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mansurjisan-ndbc-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "ndbc-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mansurjisan-ndbc-mcp --command uvx --arg ndbc-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mansurjisan-ndbc-mcp:
    command: "uvx"
    args: ["ndbc-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mansurjisan-ndbc-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "ndbc-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mansurjisan-ndbc-mcp -t stdio -c uvx -a ndbc-mcp
// mcp.json
{
  "mcpServers": {
    "mansurjisan-ndbc-mcp": {
      "command": "uvx",
      "args": [
        "ndbc-mcp"
      ]
    }
  }
}
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.

  • 19 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.

  • 18 Sept 26 −18
    • Malware scan: pass → unverified security
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +16
    • Malware scan: unverified → pass security
  • 14 Sept 26 −14
    • Malware scan: pass → unverified security
  • 12 Sept 26 +16
    • Malware scan: unverified → pass security
  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 10 Sept 26 −15
    • Malware scan: pass → unverified security
    • Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed pypi/ndbc-mcp@0.1.2

Provenance No attestation

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

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,118 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
ndbc_compare_stations ~92

Compare latest observations from multiple NDBC stations side by side. Args: station_ids: List of NDBC station IDs to compare (2-10 stations, e.g., ['41001', '41002', '44013']). response_format: Output format — 'markdown' (default) or 'json'.

NameTypeReqDescription
response_formatstring
station_idsarrayyes
NameTypeReqDescription
resultstringyes

No examples provided.

ndbc_find_nearest_stations ~200

Find NDBC stations nearest to a geographic coordinate. Args: latitude: Latitude in decimal degrees (e.g., 40.7). longitude: Longitude in decimal degrees (e.g., -74.0). radius_km: Search radius in kilometers (default 200). station_type: Optional filter by platform type (e.g., 'buoy'). has_met: If true, only stations with meteorological sensors. limit: Maximum number of stations to return (default 5). response_format: Output format — 'markdown' (default) or 'geojson' (a FeatureCollection of Point features, coordinates [lon, lat]).

NameTypeReqDescription
has_met
latitudenumberyes
limitinteger
longitudenumberyes
radius_kmnumber
response_formatstring
station_type
NameTypeReqDescription
resultstringyes

No examples provided.

ndbc_get_daily_summary ~137

Get daily min/max/mean statistics for key variables over recent days. Args: station_id: NDBC station ID (e.g., '41001', '46042'). days: Number of days to summarize (default 7, max 45). variables: Variables to include (default: WSPD, GST, WVHT, DPD, PRES, ATMP, WTMP). response_format: Output format — 'markdown' (default) or 'json'.

NameTypeReqDescription
daysinteger
response_formatstring
station_idstringyes
variables
NameTypeReqDescription
resultstringyes

No examples provided.

ndbc_get_latest_observation ~102

Get the latest observation from an NDBC station. Returns all available variables (wind, waves, temperature, pressure, etc.) as key-value pairs. Args: station_id: NDBC station ID (e.g., '41001', '46042', 'TPLM2'). response_format: Output format — 'markdown' (default) or 'json'.

NameTypeReqDescription
response_formatstring
station_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

ndbc_get_observations ~216

Get time series observations from an NDBC station. Data covers the last 45 days (rolling), updated every ~10 minutes. Args: station_id: NDBC station ID (e.g., '41001', '46042'). hours: Number of hours to retrieve (default 24, max 1080 = 45 days). variables: Optional list of variables to include (e.g., ['WSPD', 'WVHT', 'WTMP']). Default: all available. response_format: Output format — 'markdown' (default) or 'json'. max_records: Cap on JSON records returned (default 2000). A long hours window is thousands of points; only the most recent max_records are kept, and the JSON flags any truncation. (Markdown is already capped.)

NameTypeReqDescription
hoursinteger
max_recordsinteger
response_formatstring
station_idstringyes
variables
NameTypeReqDescription
resultstringyes

No examples provided.

ndbc_get_station ~55

Get metadata for a specific NDBC station. Args: station_id: NDBC station ID (e.g., '41001', '46042', 'TPLM2').

NameTypeReqDescription
station_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

ndbc_get_wave_summary ~162

Get spectral wave summary from an NDBC station. Provides swell and wind-wave separation from the .spec file. Args: station_id: NDBC station ID (e.g., '41001', '46042'). hours: Number of hours to retrieve (default 24, max 1080). response_format: Output format — 'markdown' (default) or 'json'. max_records: Cap on JSON records returned (default 2000). Only the most recent max_records are kept, and the JSON flags any truncation. (Markdown is already capped.)

NameTypeReqDescription
hoursinteger
max_recordsinteger
response_formatstring
station_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

ndbc_list_stations ~154

List active NDBC stations with optional filters. Args: station_type: Filter by platform type (e.g., 'buoy', 'fixed', 'dart', 'cman', 'tides', 'oilrig'). owner: Filter by station owner string (case-insensitive substring match, e.g., 'NDBC', 'Environment Canada'). has_met: If true, only stations with meteorological sensors. limit: Maximum stations to return (default 50). offset: Number of stations to skip for pagination (default 0).

NameTypeReqDescription
has_met
limitinteger
offsetinteger
owner
station_type
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the NOAA NDBC MCP Server server?

NOAA NDBC MCP Server is listed in the public MCP registry as io.github.mansurjisan/ndbc-mcp. NOAA National Data Buoy Center observations: waves, SST, wind, pressure from 1,300+ stations. This page covers its PyPI package (ndbc-mcp).

Is the NOAA NDBC MCP Server server safe to use?

NOAA NDBC MCP Server scores 56 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 NOAA NDBC MCP Server server expose?

NOAA NDBC MCP Server exposes 8 tools: ndbc_get_daily_summary, ndbc_compare_stations, ndbc_get_latest_observation, ndbc_get_observations, ndbc_get_wave_summary, and 3 more. Their descriptions and schemas cost roughly 1,118 tokens of context every time the server is loaded.

Is the NOAA NDBC MCP Server server still maintained?

NOAA NDBC MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.