NOAA OFS MCP Server
PYPI · OFS-MCP · SCANNED OCT 4
NOAA OFS regional ocean model forecasts — water level, temperature, salinity
Available components
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
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
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 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
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.
pypi · ofs-mcp
claude mcp add oceanmodeling-ofs-mcp -- uvx ofs-mcp
{
"mcpServers": {
"oceanmodeling-ofs-mcp": {
"command": "uvx",
"args": [
"ofs-mcp"
]
}
}
} {
"servers": {
"oceanmodeling-ofs-mcp": {
"command": "uvx",
"args": [
"ofs-mcp"
]
}
}
} codex mcp add oceanmodeling-ofs-mcp -- uvx ofs-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"oceanmodeling-ofs-mcp": {
"type": "local",
"command": [
"uvx",
"ofs-mcp"
],
"enabled": true
}
}
} openclaw mcp add oceanmodeling-ofs-mcp --command uvx --arg ofs-mcp
mcp_servers:
oceanmodeling-ofs-mcp:
command: "uvx"
args: ["ofs-mcp"] {
"McpServers": {
"oceanmodeling-ofs-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"ofs-mcp"
]
}
}
} assistant mcp add oceanmodeling-ofs-mcp -t stdio -c uvx -a ofs-mcp
{
"mcpServers": {
"oceanmodeling-ofs-mcp": {
"command": "uvx",
"args": [
"ofs-mcp"
]
}
}
} 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.
- 1 Oct 26 63
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 4 Oct 2026 · Analysed pypi/ofs-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/ofs-mcp-v0.1.1 |
| Rekor log index | 3034674648 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:b904d929a555b0f5fae59b33d58e1151f2f14ad2261d81b9d5f541b87c9b0bf2 |
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 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| 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 →
ofs_compare_with_coops ~175
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| hours_to_compare | integer | – | – |
| model | – | yes | – |
| response_format | string | – | – |
| station_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ofs_find_models_for_location ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| longitude | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ofs_get_forecast_at_point ~215
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| longitude | number | yes | – |
| max_distance_km | number | – | – |
| model | – | yes | – |
| response_format | string | – | – |
| variable | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ofs_get_model_info ~92
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| model | – | yes | – |
| response_format | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ofs_list_cycles ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | – | – | – |
| model | – | yes | – |
| num_days | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ofs_list_models ~66
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.