ADCIRC Model Setup MCP Server
PYPI · ADCIRC-MCP · SCANNED OCT 4
ADCIRC model configuration debugging, parameter lookup, and validation
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 Security100
- No malware found by supply-chain analysis.Pass
- 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 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 996 tokens (~99/item across 10 items; 10 tools + 0 resources), lean.Pass
- 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 ADCIRC Model Setup MCP Server server?
ADCIRC Model Setup MCP Server runs locally as a PyPI package, launched with uvx adcirc-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 · adcirc-mcp
claude mcp add oceanmodeling-adcirc-mcp -- uvx adcirc-mcp
{
"mcpServers": {
"oceanmodeling-adcirc-mcp": {
"command": "uvx",
"args": [
"adcirc-mcp"
]
}
}
} {
"servers": {
"oceanmodeling-adcirc-mcp": {
"command": "uvx",
"args": [
"adcirc-mcp"
]
}
}
} codex mcp add oceanmodeling-adcirc-mcp -- uvx adcirc-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"oceanmodeling-adcirc-mcp": {
"type": "local",
"command": [
"uvx",
"adcirc-mcp"
],
"enabled": true
}
}
} openclaw mcp add oceanmodeling-adcirc-mcp --command uvx --arg adcirc-mcp
mcp_servers:
oceanmodeling-adcirc-mcp:
command: "uvx"
args: ["adcirc-mcp"] {
"McpServers": {
"oceanmodeling-adcirc-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"adcirc-mcp"
]
}
}
} assistant mcp add oceanmodeling-adcirc-mcp -t stdio -c uvx -a adcirc-mcp
{
"mcpServers": {
"oceanmodeling-adcirc-mcp": {
"command": "uvx",
"args": [
"adcirc-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 78
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/adcirc-mcp@0.1.2
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/adcirc-mcp-v0.1.2 |
| Rekor log index | 3034671831 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:29d610c89ac26faa33f84dc1fe32b8ccca119954132727b985726175859f1273 |
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 28 packages
| Packages resolved | 28 |
|---|---|
| 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 →
adcirc_diagnose_error ~82
Diagnose an ADCIRC run error from a log snippet or error description. Matches against known ADCIRC failure patterns (CFL violation, hot-start issues, NWS mismatch, boundary errors, etc.) and suggests fixes. Args: error_text: Error message, log snippet, or description of the problem.
| Name | Type | Req | Description |
|---|---|---|---|
| error_text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
adcirc_explain_parameter ~102
Look up any ADCIRC fort.15 parameter by name. Returns description, valid values, typical range, common pitfalls, and companion file requirements. Also covers NWS values, tidal constituents, and nodal attributes. Args: parameter: Parameter name (e.g., 'NWS', 'DTDP', 'TAU0', 'M2', 'mannings_n_at_sea_floor').
| Name | Type | Req | Description |
|---|---|---|---|
| parameter | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
adcirc_fetch_docs ~67
Fetch documentation from the ADCIRC wiki for a specific topic. Retrieves the wiki page content as plain text. Args: topic: Wiki page title or topic (e.g., 'Fort.15', 'NWS', 'Hot Start').
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
adcirc_list_parameters ~98
List all ADCIRC fort.15 parameters grouped by category. Returns a cheat sheet of parameter names with brief descriptions. Also lists tidal constituents and nodal attributes. Args: category: Optional filter by category (e.g., 'time_stepping', 'forcing', 'friction', 'output', 'tidal', 'solver', 'wetting_drying', 'spatial', 'meteorological').
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
adcirc_parse_fort13 ~77
Parse an ADCIRC fort.13 nodal attributes file. Returns attribute names, default values, and non-default node counts. Args: file_path: Path to the fort.13 file on disk. content: Raw text content of the fort.13 file.
| Name | Type | Req | Description |
|---|---|---|---|
| content | – | – | – |
| file_path | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
adcirc_parse_fort14 ~98
Parse an ADCIRC fort.14 mesh file header (NOT the full mesh). Returns grid name, node count, element count, and boundary information. Does NOT load node coordinates or element connectivity into memory. Args: file_path: Path to the fort.14 file on disk. content: Raw text content (or header portion) of the fort.14 file.
| Name | Type | Req | Description |
|---|---|---|---|
| content | – | – | – |
| file_path | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
adcirc_parse_fort15 ~94
Parse an ADCIRC fort.15 control file into a structured summary. Extracts run parameters, timestep, forcing configuration, tidal constituents, output settings, and station locations. Args: file_path: Path to the fort.15 file on disk. content: Raw text content of the fort.15 file (alternative to file_path).
| Name | Type | Req | Description |
|---|---|---|---|
| content | – | – | – |
| file_path | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
adcirc_parse_fort22 ~106
Parse an ADCIRC fort.22 meteorological forcing file header. Returns format type, time range, and spatial extent based on the NWS value. Args: nws: NWS value from fort.15 (determines the file format). file_path: Path to the fort.22 file on disk. content: Raw text content of the fort.22 file.
| Name | Type | Req | Description |
|---|---|---|---|
| content | – | – | – |
| file_path | – | – | – |
| nws | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
adcirc_search_docs ~75
Search the ADCIRC wiki and return matching pages with summaries. Args: query: Search terms (e.g., 'tidal forcing', 'hot start', 'wetting drying'). limit: Maximum number of results to return (default 10).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
adcirc_validate_config ~197
Validate an ADCIRC configuration with comprehensive checks. Parses fort.15 and optionally cross-references with fort.14 and fort.13. Checks CFL condition, parameter consistency, NWS/file matching, DRAMP adequacy, station counts, and output frequency sanity. Args: fort15_path: Path to the fort.15 file. fort15_content: Raw text of fort.15 (alternative to path). fort14_path: Optional path to fort.14 for cross-validation. fort13_path: Optional path to fort.13 for cross-validation. min_edge_length: Optional minimum mesh edge length in meters (for CFL check). max_depth: Optional maximum water depth in meters (for CFL check).
| Name | Type | Req | Description |
|---|---|---|---|
| fort13_path | – | – | – |
| fort14_path | – | – | – |
| fort15_content | – | – | – |
| fort15_path | – | – | – |
| max_depth | – | – | – |
| min_edge_length | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the ADCIRC Model Setup MCP Server server?
ADCIRC Model Setup MCP Server is listed in the public MCP registry as io.github.oceanmodeling/adcirc-mcp. ADCIRC model configuration debugging, parameter lookup, and validation. This page covers its PyPI package (adcirc-mcp).
Is the ADCIRC Model Setup MCP Server server safe to use?
ADCIRC Model Setup MCP Server scores 78 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 ADCIRC Model Setup MCP Server server expose?
ADCIRC Model Setup MCP Server exposes 10 tools: adcirc_fetch_docs, adcirc_search_docs, adcirc_parse_fort15, adcirc_parse_fort14, adcirc_parse_fort13, and 5 more. Their descriptions and schemas cost roughly 996 tokens of context every time the server is loaded.
Is the ADCIRC Model Setup MCP Server server still maintained?
ADCIRC Model Setup 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 ADCIRC Model Setup MCP Server server under?
ADCIRC Model Setup 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.