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.

NHC MCP Server

PYPI · NHC-MCP

NHC storm tracks, forecast advisories, watches/warnings, and HURDAT2 data

Available components

−15 this week 77 Trust /100

Last scanned (15 hours ago)

Scores higher than 71% of PyPI servers

Category Maps and Location

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 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 50 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 814 tokens (~162/item across 5 items; 5 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 9 Nov 26 +21
    • Malware scan: unverified → pass ▲ security
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 7 Nov 26 −14
    • Malware scan: pass → unverified ▼ 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 21 Nov 2026 · Analysed pypi/nhc-mcp@0.1.1

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/nhc-mcp-v0.1.1
Rekor log index 3034474626
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:674475a7a8a13fea727576ae86a8eb912ed3c03875575f174c7a33b1e333686e

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool 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 →

MCP tools · 5 exposed · ~814 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
nhc_get_active_storms ~87

Get currently active tropical cyclones from the National Hurricane Center. Returns a list of all active storms with their current classification, location, and advisory information. Returns an empty list outside of hurricane season or when no storms are active. Args: response_format: Output format — 'markdown' (default) or 'json'.

NameTypeReqDescription
response_formatstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

nhc_get_best_track ~166

Get best track (observed path) data for a tropical cyclone. For recent storms (current/previous year), retrieves from ATCF B-deck files. For historical storms, retrieves from HURDAT2 archive (Atlantic 1851–2024, East Pacific 1949–2024). Args: storm_id: NHC storm identifier (e.g., 'AL092005' for Katrina, 'AL042024'). response_format: Output format — 'markdown' (default), 'json', or 'geojson' (a FeatureCollection: a LineString for the track plus a Point per fix, coordinates [lon, lat], for mapping).

NameTypeReqDescription
response_formatstring––
storm_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

nhc_get_forecast_track ~199

Get the official NHC 5-day forecast track positions for an active storm. Retrieves forecast point data from the NHC ArcGIS MapServer including position (lat/lon), forecast time, maximum winds, development type, and Saffir-Simpson category for each forecast period (12h, 24h, etc.). Note: This only works for currently active storms. Use nhc_get_active_storms first to see available storms and their IDs. Args: storm_id: NHC storm identifier (e.g., 'AL052024', 'EP042023'). response_format: Output format — 'markdown' (default), 'json', or 'geojson' (a FeatureCollection: a LineString for the forecast track plus a Point per forecast period, coordinates [lon, lat]).

NameTypeReqDescription
response_formatstring––
storm_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

nhc_get_storm_watches_warnings ~136

Get active watches and warnings for an active tropical cyclone. Returns coastal watch/warning segments (Hurricane Warning, Tropical Storm Watch, etc.) from the NHC ArcGIS MapServer. Note: This only works for currently active storms with watches/warnings in effect. Use nhc_get_active_storms first to see available storms. Args: storm_id: NHC storm identifier (e.g., 'AL052024'). response_format: Output format — 'markdown' (default) or 'json'.

NameTypeReqDescription
response_formatstring––
storm_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

nhc_search_storms ~226

Search historical tropical cyclones in the HURDAT2 database. Searches the Atlantic (1851–2024) and East Pacific (1949–2024) hurricane databases. Filter by storm name, year, basin, and/or minimum wind speed. Args: name: Storm name to search for (case-insensitive, partial match). E.g., 'katrina'. year: Filter by year (e.g., 2005). basin: Filter by basin — 'al' (Atlantic), 'ep' (East Pacific), 'cp' (Central Pacific). min_wind: Minimum peak wind speed in knots (e.g., 64 for hurricanes, 96 for major). limit: Maximum number of results to return (default 50). response_format: Output format — 'markdown' (default) or 'json'.

NameTypeReqDescription
basin–––
limitinteger––
min_wind–––
name–––
response_formatstring––
year–––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the NHC MCP Server server?

NHC MCP Server runs locally as a PyPI package, launched with uvx nhc-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 · nhc-mcp

# add to Claude Code
claude mcp add oceanmodeling-nhc-mcp -- uvx nhc-mcp
Common questions

What is the NHC MCP Server server?

NHC MCP Server is listed in the public MCP registry as io.github.oceanmodeling/nhc-mcp. NHC storm tracks, forecast advisories, watches/warnings, and HURDAT2 data. This page covers its PyPI package (nhc-mcp).

Is the NHC MCP Server server safe to use?

NHC MCP Server scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 NHC MCP Server server expose?

NHC MCP Server exposes 5 tools: nhc_get_active_storms, nhc_get_forecast_track, nhc_get_storm_watches_warnings, nhc_get_best_track, nhc_search_storms. Their descriptions and schemas cost roughly 814 tokens of context every time the server is loaded.

Is the NHC MCP Server server still maintained?

NHC MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 November 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 NHC MCP Server server under?

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

What did VerifyMCP test on the NHC MCP Server server?

VerifyMCP ran 15 checks on NHC MCP Server, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about NHC MCP Server: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.