# NOAA OFS MCP Server (pypi · ofs-mcp)

NOAA OFS regional ocean model forecasts — water level, temperature, salinity

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

## Components

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

## Channel facts

- Registry: `pypi`
- Package: `ofs-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**: 50/100
  - Malware scan not yet available for this package.
  - 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.
  - 1 of 31 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**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 767 tokens (~127/item across 6 items; 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 NOAA OFS MCP Server server?

NOAA OFS MCP Server runs locally as a PyPI package, launched with uvx ofs-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-ofs-mcp -- uvx ofs-mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "oceanmodeling-ofs-mcp": {
      "command": "uvx",
      "args": [
        "ofs-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-01 (score 63)

First indexed and scored.

## MCP tools (6)

### `ofs_list_models` (~66 tokens)

List all supported NOAA OFS regional ocean models with key metadata.

Returns model names, grid types, geographic coverage, cycle schedules,
forecast lengths, and variables available.

Args:
    response_format: 'markdown' (default) or 'json'.

Input parameters:

- `response_format` (string)

Output parameters:

- `result` (string)

### `ofs_get_model_info` (~92 tokens)

Get detailed specifications for a specific OFS model.

Returns grid type, spatial domain, cycle schedule, vertical levels,
datum, available variables, and data access URLs.

Args:
    model: OFS model identifier (e.g., 'cbofs', 'ngofs2').
    response_format: 'markdown' (default) or 'json'.

Input parameters:

- `model` (required)
- `response_format` (string)

Output parameters:

- `result` (string)

### `ofs_list_cycles` (~129 tokens)

List available OFS forecast cycles on AWS S3 for a given model and date range.

Checks S3 for available forecast files to determine which cycles have been
published. Useful before calling ofs_get_forecast_at_point.

Args:
    model: OFS model identifier (e.g., 'cbofs', 'ngofs2').
    date: Specific date in YYYY-MM-DD format. Default: today UTC.
    num_days: Number of past days to check (1–7). Default: 2.

Input parameters:

- `date`
- `model` (required)
- `num_days` (integer)

Output parameters:

- `result` (string)

### `ofs_find_models_for_location` (~90 tokens)

Find which OFS models cover a given latitude/longitude location.

Uses model bounding boxes to identify all models whose domain includes
the specified point. Larger regional models may cover the area at
coarser resolution than smaller local models.

Args:
    latitude: Latitude in decimal degrees.
    longitude: Longitude in decimal degrees.

Input parameters:

- `latitude` (number, required)
- `longitude` (number, required)

Output parameters:

- `result` (string)

### `ofs_get_forecast_at_point` (~215 tokens)

Get an OFS model forecast time series at a geographic point.

Connects to the NOAA THREDDS OPeNDAP server to lazily extract the
forecast at the nearest model grid point without downloading the full
gridded file. Falls back to S3 download if OPeNDAP is unavailable.

Args:
    latitude: Target latitude in decimal degrees.
    longitude: Target longitude in decimal degrees.
    model: OFS model to query (e.g., 'cbofs', 'ngofs2', 'wcofs').
    variable: Variable to retrieve — 'water_level', 'temperature', or 'salinity'.
    max_distance_km: Maximum distance to nearest grid point in km (default 100).
    response_format: 'markdown' (default) or 'json'.

Input parameters:

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

Output parameters:

- `result` (string)

### `ofs_compare_with_coops` (~175 tokens)

Compare OFS model water level forecast against CO-OPS observations at a station.

Fetches the model forecast at the nearest grid point to the CO-OPS station
and compares it with the observed water level. Computes bias, RMSE, MAE,
peak error, and correlation.

Args:
    station_id: CO-OPS station ID (e.g., '8571892' for Cambridge, MD).
    model: OFS model identifier (e.g., 'cbofs', 'ngofs2').
    hours_to_compare: Hours of comparison period (default 24, max 96).
    response_format: 'markdown' (default) or 'json'.

Input parameters:

- `hours_to_compare` (integer)
- `model` (required)
- `response_format` (string)
- `station_id` (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-ofs-mcp/ofs-mcp#diagnostics

## Score history

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

## Common questions

### What is the NOAA OFS MCP Server server?

NOAA OFS MCP Server is listed in the public MCP registry as io.github.oceanmodeling/ofs-mcp. NOAA OFS regional ocean model forecasts, water level, temperature, salinity. This page covers its PyPI package (ofs-mcp).

### Is the NOAA OFS MCP Server server safe to use?

NOAA OFS MCP Server scores 63 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 NOAA OFS MCP Server server expose?

NOAA OFS MCP Server exposes 6 tools: ofs_list_models, ofs_get_model_info, ofs_list_cycles, ofs_find_models_for_location, ofs_get_forecast_at_point, ofs_compare_with_coops. Their descriptions and schemas cost roughly 767 tokens of context every time the server is loaded.

### Is the NOAA OFS MCP Server server still maintained?

NOAA OFS 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 NOAA OFS MCP Server server under?

NOAA OFS 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/ofs-mcp/
- Socket report: https://socket.dev/pypi/package/ofs-mcp
- Repository: https://github.com/oceanmodeling/ocean-mcp
- Changelog RSS feed: https://verifymcp.io/servers/oceanmodeling-ofs-mcp/ofs-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/oceanmodeling-ofs-mcp/ofs-mcp.json
- HTML version of this page: https://verifymcp.io/servers/oceanmodeling-ofs-mcp/ofs-mcp