# NOAA RTOFS MCP Server (pypi · rtofs-mcp)

NOAA RTOFS global ocean forecast — SST, salinity, currents, depth profiles via HYCOM THREDDS

- Trust score: 83/100 (high trust)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

> **Recent critical change**: GHSA-6q48-6c7w-9gw2 affects this package (2026-10-21). See the changelog below before you install this server.

## Components

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

## Channel facts

- Registry: `pypi`
- Package: `rtofs-mcp`
- Version: `0.1.3`
- 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-25.

- **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 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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.

## Install

### 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.

### Claude

```bash
claude mcp add oceanmodeling-rtofs-mcp -- uvx rtofs-mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "oceanmodeling-rtofs-mcp": {
      "command": "uvx",
      "args": [
        "rtofs-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-25 (score 83, +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.

### 2026-10-22 (score 82, +82)

- [security improvement] GHSA-6q48-6c7w-9gw2 no longer affects this package
- [security improvement] Known CVEs: fail → pass
- [functional improvement] Stability: unverified → 0.27
- [functional improvement] Score status: failed → scored

### 2026-10-21 (score 0, −78)

- [critical regression] GHSA-6q48-6c7w-9gw2 affects this package: none
- [critical regression] Known CVEs: pass → fail
- [critical regression] Score status: scored → failed

### 2026-10-14 (score 78)

First indexed and scored.

## MCP tools (8)

### `rtofs_get_transect` (~235 tokens)

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'.

Input parameters:

- `lat_end` (number, required)
- `lat_start` (number, required)
- `lon_end` (number, required)
- `lon_start` (number, required)
- `n_points` (integer)
- `response_format` (string)
- `time`
- `variable` (string)

Output parameters:

- `result` (string)

### `rtofs_compare_with_observations` (~165 tokens)

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'.

Input parameters:

- `latitude` (number, required)
- `longitude` (number, required)
- `response_format` (string)
- `time`
- `variable` (string)

Output parameters:

- `result` (string)

### `rtofs_get_system_info` (~91 tokens)

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'.

Input parameters:

- `response_format` (string)

Output parameters:

- `result` (string)

### `rtofs_list_datasets` (~111 tokens)

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'.

Input parameters:

- `check_availability` (boolean)
- `response_format` (string)

Output parameters:

- `result` (string)

### `rtofs_get_latest_time` (~94 tokens)

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'.

Input parameters:

- `dataset` (string)
- `response_format` (string)

Output parameters:

- `result` (string)

### `rtofs_get_surface_forecast` (~344 tokens)

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'.

Input parameters:

- `latitude` (number, required)
- `longitude` (number, required)
- `response_format` (string)
- `time_end`
- `time_start`
- `variable` (string)

Output parameters:

- `result` (string)

### `rtofs_get_profile_forecast` (~193 tokens)

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'.

Input parameters:

- `latitude` (number, required)
- `longitude` (number, required)
- `response_format` (string)
- `time`
- `variable` (string)

Output parameters:

- `result` (string)

### `rtofs_get_area_forecast` (~259 tokens)

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'.

Input parameters:

- `lat_end` (number, required)
- `lat_start` (number, required)
- `lon_end` (number, required)
- `lon_start` (number, required)
- `n_points` (integer)
- `response_format` (string)
- `time`
- `variable` (string)

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-10-25: 83
- 2026-10-24: 82
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 0
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 78

## Common questions

### 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.

## Links

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