# NOAA Recon MCP Server (pypi · recon-mcp)

Hurricane reconnaissance data — HDOB flight observations, Vortex Data Messages, SFMR, and ATCF fixes

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

## Components

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

## Channel facts

- Registry: `pypi`
- Package: `recon-mcp`
- Version: `0.1.2`
- 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 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1781 tokens (~296/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 Recon MCP Server server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "oceanmodeling-recon-mcp": {
      "command": "uvx",
      "args": [
        "recon-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 62)

First indexed and scored.

## MCP tools (6)

### `recon_get_fixes` (~230 tokens)

Get ATCF f-deck aircraft fix data for a tropical cyclone.

F-deck data contains structured aircraft and satellite position fixes
including lat/lon, wind speed, and pressure. This is the most
machine-readable format for reconnaissance fix data.

Args:
    basin: Basin code — 'al' (Atlantic), 'ep' (East Pacific), or 'cp' (Central Pacific).
    storm_number: Storm number within the season (e.g., 14 for AL142024).
    year: 4-digit year (e.g., 2024).
    max_records: Cap on fix records returned (default 2000). The f-deck
        is served chronologically oldest-first, so only the most recent
        max_records fixes are kept, and the output flags any
        truncation.
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `basin` (string, required)
- `max_records` (integer)
- `response_format` (string)
- `storm_number` (integer, required)
- `year` (integer, required)

Output parameters:

- `result` (string)

### `recon_get_hdobs` (~263 tokens)

Get HDOB (High Density Observation) flight-level reconnaissance data.

HDOB bulletins contain 30-second averaged observations from hurricane
hunter aircraft including flight-level winds, SFMR surface winds,
pressure, temperature, and position. This is the primary real-time
reconnaissance data feed.

Args:
    year: Year of data (e.g., 2024).
    basin: Basin — 'al' (Atlantic, default), 'ep' (East Pacific), or 'cp' (Central Pacific).
    month: Optional month filter (1-12).
    day: Optional day filter (1-31).
    limit: Maximum number of HDOB bulletins to parse (default 20).
    max_records: Cap on observations returned (default 2000). Bulletins
        are already fetched newest-first, so only the most recent
        max_records observations are kept, and the output flags any
        truncation.
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `basin` (string)
- `day`
- `limit` (integer)
- `max_records` (integer)
- `month`
- `response_format` (string)
- `year` (integer, required)

Output parameters:

- `result` (string)

### `recon_list_missions` (~289 tokens)

List available reconnaissance data files from the NHC archive.

Browse the NHC reconnaissance archive directory for HDOB, VDM, or
dropsonde bulletins. Use this to discover what data files exist
before fetching specific observations.

Args:
    year: Year to search (e.g., 2024).
    product: Data product type — 'hdob', 'vdm', or 'dropsonde'.
    basin: Basin — 'al' (Atlantic, default), 'ep' (East Pacific), or 'cp' (Central Pacific).
    month: Optional month filter (1-12) to narrow results by filename date.
    day: Optional day filter (1-31) to narrow results by filename date.
    limit: Maximum number of files to return (default 50).
    max_records: Cap on files returned (default 2000). Entries are
        already sorted newest-filename-first, so only the most recent
        max_records files are kept, and the output flags any
        truncation.
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `basin` (string)
- `day`
- `limit` (integer)
- `max_records` (integer)
- `month`
- `product` (string, required)
- `response_format` (string)
- `year` (integer, required)

Output parameters:

- `result` (string)

### `recon_list_sfmr` (~228 tokens)

List available SFMR NetCDF files for a storm from the AOML archive.

SFMR (Stepped-Frequency Microwave Radiometer) files contain 1-Hz
surface wind speed and rain rate observations from hurricane hunter
aircraft. Data is post-processed and quality-controlled by AOML/HRD.

Note: AOML posts data weeks to months after storms. Recent storms
may not have SFMR data available yet.

Args:
    year: Year of the storm (e.g., 2022).
    storm_name: Lowercase storm name (e.g., 'ian', 'laura').
    max_records: Cap on files returned in JSON output (default 2000).
        Files are listed oldest-first, so only the most recent
        max_records are kept, and the output flags any truncation.
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `max_records` (integer)
- `response_format` (string)
- `storm_name` (string, required)
- `year` (integer, required)

Output parameters:

- `result` (string)

### `recon_get_sfmr` (~473 tokens)

Get SFMR radial wind profile for a storm — surface wind speed vs. distance from center.

Downloads SFMR NetCDF data from the AOML archive and computes each
observation's radial distance from the storm center using the ATCF
best track. Returns binned wind statistics (mean, max, count) by
radius.

Requires the storm's ATCF identifiers (basin + storm_number) to
fetch the best track for radius computation.

Note: AOML posts data weeks to months after storms. Recent storms
may not have SFMR data available yet.

Args:
    year: Year of the storm (e.g., 2022).
    storm_name: Lowercase storm name (e.g., 'ian', 'laura').
    storm_number: ATCF storm number within the season (e.g., 9 for AL09).
    basin: Basin code — 'al' (Atlantic, default), 'ep' (East Pacific).
    filename: Specific SFMR filename to process. If None, processes up
        to max_records files.
    bin_size_km: Radial bin width in km (default 5).
    max_radius_km: Maximum radius to include in km (default 500).
    max_records: Cap on SFMR NetCDF files downloaded and processed
        (default 10). Each file triggers a network download and NetCDF
        parse, so unlike other recon tools' output caps this also
        bounds request volume — files are decoded and sorted by their
        embedded flight date, and the most recent max_records are kept.
        (AOML's raw directory listing is grouped by agency prefix,
        e.g. all AFRC_* entries before NOAA_*, not chronological order,
        so the date must be decoded from each filename first.)
        Ignored when filename is given.
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `basin` (string)
- `bin_size_km` (number)
- `filename`
- `max_radius_km` (number)
- `max_records` (integer)
- `response_format` (string)
- `storm_name` (string, required)
- `storm_number` (integer, required)
- `year` (integer, required)

Output parameters:

- `result` (string)

### `recon_get_vdms` (~298 tokens)

Get Vortex Data Messages (VDMs) — storm center fix reports from recon aircraft.

VDMs contain the most operationally critical reconnaissance data: center
position, minimum sea-level pressure, max flight-level and surface winds,
eye diameter, and storm structure. Each VDM represents a single pass
through or near the storm center.

Args:
    year: Year of data (e.g., 2024).
    basin: Basin — 'al' (Atlantic, default), 'ep' (East Pacific), or 'cp' (Central Pacific).
    storm_id: Optional storm ID filter (e.g., 'AL142024' for Milton).
    month: Optional month filter (1-12).
    day: Optional day filter (1-31).
    limit: Maximum number of VDMs to parse (default 50).
    max_records: Cap on VDMs returned (default 2000). Files are already
        fetched newest-first, so only the most recent max_records VDMs
        are kept, and the output flags any truncation.
    response_format: Output format — 'markdown' (default) or 'json'.

Input parameters:

- `basin` (string)
- `day`
- `limit` (integer)
- `max_records` (integer)
- `month`
- `response_format` (string)
- `storm_id`
- `year` (integer, 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-recon-mcp/recon-mcp#diagnostics

## Score history

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

## Common questions

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

NOAA Recon MCP Server is listed in the public MCP registry as io.github.oceanmodeling/recon-mcp. Hurricane reconnaissance data, HDOB flight observations, Vortex Data Messages, SFMR, and ATCF fixes. This page covers its PyPI package (recon-mcp).

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

NOAA Recon MCP Server scores 62 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 Recon MCP Server server expose?

NOAA Recon MCP Server exposes 6 tools: recon_get_fixes, recon_get_hdobs, recon_list_missions, recon_list_sfmr, recon_get_sfmr, recon_get_vdms. Their descriptions and schemas cost roughly 1,781 tokens of context every time the server is loaded.

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

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

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