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.

SCHISM Model Setup MCP Server

PYPI · SCHISM-MCP · SCANNED OCT 4

SCHISM model configuration debugging, parameter lookup, and validation

Available components

78 Trust /100
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 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 834 tokens (~83/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.

Install

How do I install the SCHISM Model Setup MCP Server server?

SCHISM Model Setup MCP Server runs locally as a PyPI package, launched with uvx schism-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 · schism-mcp

# add to Claude Code
claude mcp add oceanmodeling-schism-mcp -- uvx schism-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "oceanmodeling-schism-mcp": {
      "command": "uvx",
      "args": [
        "schism-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "oceanmodeling-schism-mcp": {
      "command": "uvx",
      "args": [
        "schism-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add oceanmodeling-schism-mcp -- uvx schism-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "oceanmodeling-schism-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "schism-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add oceanmodeling-schism-mcp --command uvx --arg schism-mcp
# ~/.hermes/config.yaml
mcp_servers:
  oceanmodeling-schism-mcp:
    command: "uvx"
    args: ["schism-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "oceanmodeling-schism-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "schism-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add oceanmodeling-schism-mcp -t stdio -c uvx -a schism-mcp
// mcp.json
{
  "mcpServers": {
    "oceanmodeling-schism-mcp": {
      "command": "uvx",
      "args": [
        "schism-mcp"
      ]
    }
  }
}
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.

  • 4 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 1 Oct 26 63

    First indexed and scored.

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 4 Oct 2026 · Analysed pypi/schism-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/schism-mcp-v0.1.1
Rekor log index 3034672927
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:c369b09a68695f9a1de9cebc17cb92b89bee4e3dcb3ae8985dc9fa240729ef94

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 →

MCP tools · 10 exposed · ~834 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
schism_diagnose_error ~82

Diagnose a SCHISM run error from a log snippet or error description. Matches against known SCHISM failure modes (dry boundary, NaN, vertical instability, hotstart incompatibility, etc.) and suggests fixes. Args: error_text: Error message, log snippet, or description of the problem.

NameTypeReqDescription
error_textstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

schism_explain_parameter ~95

Look up any SCHISM param.nml parameter by name. Returns namelist section, description, valid values, default, and common mistakes. Also covers tidal constituents, vertical grid types, and boundary condition types. Args: parameter: Parameter name (e.g., 'dt', 'nspool', 'ihfskip', 'M2', 'LSC2').

NameTypeReqDescription
parameterstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

schism_fetch_docs ~61

Fetch documentation from the SCHISM documentation site. Retrieves page content as plain text. Args: topic: Documentation path or topic (e.g., 'input-output/param.html', 'known_issues.html').

NameTypeReqDescription
topicstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

schism_list_parameters ~57

List all SCHISM param.nml parameters grouped by section. Returns a reference of parameter names with brief descriptions. Args: section: Optional filter by section ('CORE', 'OPT', 'SCHOUT').

NameTypeReqDescription
section–––
NameTypeReqDescription
resultstringyes–

No examples provided.

schism_parse_bctides ~80

Parse a SCHISM bctides.in tidal boundary condition file. Returns tidal constituent names/frequencies, boundary segment types, and node counts. Args: file_path: Path to the bctides.in file on disk. content: Raw text content of bctides.in.

NameTypeReqDescription
content–––
file_path–––
NameTypeReqDescription
resultstringyes–

No examples provided.

schism_parse_hgrid ~90

Parse a SCHISM hgrid.gr3 horizontal grid file header. Returns node/element counts, bounding box, and boundary info. Does NOT load full mesh into memory. Args: file_path: Path to the hgrid.gr3 file on disk. content: Raw text content (or header portion) of hgrid.gr3.

NameTypeReqDescription
content–––
file_path–––
NameTypeReqDescription
resultstringyes–

No examples provided.

schism_parse_param_nml ~77

Parse a SCHISM param.nml FORTRAN namelist file. Returns all parameters organized by section with annotations. Args: file_path: Path to the param.nml file on disk. content: Raw text content of param.nml (alternative to file_path).

NameTypeReqDescription
content–––
file_path–––
NameTypeReqDescription
resultstringyes–

No examples provided.

schism_parse_vgrid ~78

Parse a SCHISM vgrid.in vertical grid file. Returns grid type (LSC2/SZ), number of levels, and layer distribution. Args: file_path: Path to the vgrid.in file on disk. content: Raw text content of vgrid.in.

NameTypeReqDescription
content–––
file_path–––
NameTypeReqDescription
resultstringyes–

No examples provided.

schism_search_docs ~51

Search SCHISM documentation and return matching pages. Args: query: Search terms (e.g., 'param.nml', 'vertical grid', 'hotstart').

NameTypeReqDescription
querystringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

schism_validate_config ~163

Validate a SCHISM configuration with comprehensive checks. Parses param.nml and optionally cross-references with hgrid.gr3 and vgrid.in. Checks nspool/ihfskip divisibility, 2D vs 3D consistency, dt adequacy, output frequency, and module flags. Args: param_nml_path: Path to param.nml file. param_nml_content: Raw text of param.nml (alternative to path). hgrid_path: Optional path to hgrid.gr3 for cross-validation. vgrid_path: Optional path to vgrid.in for cross-validation.

NameTypeReqDescription
hgrid_path–––
param_nml_content–––
param_nml_path–––
vgrid_path–––
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the SCHISM Model Setup MCP Server server?

SCHISM Model Setup MCP Server is listed in the public MCP registry as io.github.oceanmodeling/schism-mcp. SCHISM model configuration debugging, parameter lookup, and validation. This page covers its PyPI package (schism-mcp).

Is the SCHISM Model Setup MCP Server server safe to use?

SCHISM 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 SCHISM Model Setup MCP Server server expose?

SCHISM Model Setup MCP Server exposes 10 tools: schism_fetch_docs, schism_search_docs, schism_parse_param_nml, schism_parse_hgrid, schism_parse_vgrid, and 5 more. Their descriptions and schemas cost roughly 834 tokens of context every time the server is loaded.

Is the SCHISM Model Setup MCP Server server still maintained?

SCHISM 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 SCHISM Model Setup MCP Server server under?

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