NOAA RTOFS MCP Server
PYPI · RTOFS-MCP
NOAA RTOFS global ocean forecast — SST, salinity, currents, depth profiles via HYCOM THREDDS
Available components
Last scanned (24 minutes ago)
Scores higher than 83% of PyPI servers
Category Maps and Location
Recent critical change
GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.
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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to oceanmodeling/ocean-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1492 tokens (~186/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 Management37
- Stability observed for 11 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
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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +82
- GHSA-6q48-6c7w-9gw2 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- Stability: unverified → 0.27 ▲ functional
- Score status: failed → scored ▲ functional
- 21 Oct 26 −78
- GHSA-6q48-6c7w-9gw2 affects this package: none ▼ critical
- Known CVEs: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- 14 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 25 Oct 2026 · Analysed pypi/rtofs-mcp@0.1.3
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | oceanmodeling/ocean-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/oceanmodeling/ocean-mcp/.github/workflows/publish.yml@refs/tags/rtofs-mcp-v0.1.3 |
| Rekor log index | 3248719462 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:69f776b84a09ba48a8d966632e1a9b5aa125c6522da3722bbba30b08b76b88ae |
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 28 packages
| Packages resolved | 28 |
|---|---|
| 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 →
rtofs_compare_with_observations ~165
Compare RTOFS values at the same location over the 24 hours before a time. Fetches the 24 h window ending at the reference time and reports the value at its start, middle and end, plus the change across the window. Args: latitude: Latitude in decimal degrees. longitude: Longitude in decimal degrees. variable: Surface variable to compare. Default: 'sst'. time: Reference time (end of the window) in ISO format. Default: now ('present'). response_format: 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| longitude | number | yes | – |
| response_format | string | – | – |
| time | – | – | – |
| variable | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rtofs_get_area_forecast ~259
Get RTOFS surface forecast for a grid of points in a bounding box. Queries multiple points in parallel using THREDDS NCSS. The number of points per axis is controlled by n_points (total queries = n_points^2). For 3D variables (SST, SSS, currents), surface values (depth=0) are returned. Args: lat_start: Southern latitude bound. lat_end: Northern latitude bound. lon_start: Western longitude bound. lon_end: Eastern longitude bound. variable: One of: sst, sss, u_current, v_current, ssh. Default: 'sst'. time: Time in ISO format. Default: latest ('present'). n_points: Number of grid points per axis (2–15). Default: 10. Total = n^2. response_format: 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| lat_end | number | yes | – |
| lat_start | number | yes | – |
| lon_end | number | yes | – |
| lon_start | number | yes | – |
| n_points | integer | – | – |
| response_format | string | – | – |
| time | – | – | – |
| variable | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rtofs_get_latest_time ~94
Query the latest available forecast time from HYCOM THREDDS. Useful for determining what forecast data is currently available before making data queries. Args: dataset: One of 'ssh', 'sst', 'sss', 'currents'. Default: 'ssh'. response_format: 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | – | – |
| response_format | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rtofs_get_profile_forecast ~193
Get RTOFS 3D depth profile at a point (temperature, salinity, or currents vs depth). Queries HYCOM THREDDS NCSS for a vertical profile at the nearest grid cell. Returns values at all available depth levels for a single time step. Args: latitude: Latitude in decimal degrees (-80 to 90). longitude: Longitude in decimal degrees (-180 to 180). variable: One of: temperature, salinity, u, v. Default: 'temperature'. time: Time in ISO format (e.g., '2026-03-03T12:00:00Z'). Default: latest. response_format: 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| longitude | number | yes | – |
| response_format | string | – | – |
| time | – | – | – |
| variable | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rtofs_get_surface_forecast ~344
Get RTOFS surface time series at a point (SST, SSS, currents, or SSH). Queries HYCOM THREDDS NCSS for the nearest grid cell to the requested lat/lon (~8 km resolution). By default returns the window starting now: the next 72 h for the 3-hourly sst/sss/currents, the next 24 h for hourly ssh. Data spans ~10 days back and ~6 days ahead. HYCOM extracts about one time step per second, so keep custom windows to a few days. For 3D variables (SST, SSS, currents), surface values (depth=0) are returned. Args: latitude: Latitude in decimal degrees (-80 to 90). longitude: Longitude in decimal degrees (-180 to 180). variable: One of: sst, sss, u_current, v_current, ssh. Default: 'sst'. time_start: Start time in ISO format (e.g., '2026-03-01T00:00:00Z'). Default: now ('present'), or the default window before time_end when only time_end is given. time_end: End time in ISO format. Default: the default window (72 h, or 24 h for ssh) after time_start. response_format: 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| longitude | number | yes | – |
| response_format | string | – | – |
| time_end | – | – | – |
| time_start | – | – | – |
| variable | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rtofs_get_system_info ~91
Get RTOFS system overview — model specifications, variables, resolution, and coverage. Returns metadata about the Real-Time Ocean Forecast System (RTOFS/ESPC) including model resolution, forecast length, available variables, and data source information. No network request needed. Args: response_format: 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rtofs_get_transect ~235
Get a vertical transect (cross-section) between two points from RTOFS 3D data. Queries depth profiles at multiple points along a line between start and end coordinates, then combines them into a depth vs. distance cross-section. Uses asyncio.gather for parallel THREDDS NCSS queries. Args: lat_start: Starting latitude. lon_start: Starting longitude. lat_end: Ending latitude. lon_end: Ending longitude. variable: One of: temperature, salinity, u, v. Default: 'temperature'. time: Time in ISO format. Default: latest ('present'). n_points: Number of profile points along the transect (2–20). Default: 10. response_format: 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| lat_end | number | yes | – |
| lat_start | number | yes | – |
| lon_end | number | yes | – |
| lon_start | number | yes | – |
| n_points | integer | – | – |
| response_format | string | – | – |
| time | – | – | – |
| variable | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rtofs_list_datasets ~111
List RTOFS datasets on HYCOM THREDDS with optional availability check. Shows the 4 RTOFS/ESPC datasets (SSH, temperature, salinity, currents) and optionally checks if each is currently accessible. Args: check_availability: If True, ping each dataset to check live status. Default: True. response_format: 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| check_availability | boolean | – | – |
| response_format | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the NOAA RTOFS MCP Server server?
NOAA RTOFS MCP Server runs locally as a PyPI package, launched with uvx rtofs-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 · rtofs-mcp
claude mcp add oceanmodeling-rtofs-mcp -- uvx rtofs-mcp
What is the NOAA RTOFS MCP Server server?
NOAA RTOFS MCP Server is listed in the public MCP registry as io.github.oceanmodeling/rtofs-mcp. NOAA RTOFS global ocean forecast, SST, salinity, currents, depth profiles via HYCOM THREDDS. This page covers its PyPI package (rtofs-mcp).
Is the NOAA RTOFS MCP Server server safe to use?
NOAA RTOFS MCP Server scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 NOAA RTOFS MCP Server server expose?
NOAA RTOFS MCP Server exposes 8 tools: rtofs_get_transect, rtofs_compare_with_observations, rtofs_get_system_info, rtofs_list_datasets, rtofs_get_latest_time, and 3 more. Their descriptions and schemas cost roughly 1,492 tokens of context every time the server is loaded.
Is the NOAA RTOFS MCP Server server still maintained?
NOAA RTOFS MCP Server is still listed as active in the MCP registry. We last reached this channel on 25 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 NOAA RTOFS MCP Server server under?
NOAA RTOFS 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.