Use in your browser
Check one public netCDF URL with IOOS compliance-checker 6.1.0, or compare two revisions from the same dataset lineage. Get CF findings and per-check evidence without uploading a file.
Guest includes 50 lifetime app requests. Create a free account for 100 app requests each calendar month. One allowance across every app, in your browser and your agent.One allowance across every app, in your browser and your agent. Manage usage
Guest access is available after setup. Full account linking verified by PowMCP: Claude only.
Connect this app on its own. Add other PowMCP apps whenever your agent needs another job done.
Open the apps workspace
Choose your agent. Each button opens a new tab with only this app's endpoint ready to add.
ClaudeOpen Claude setup Guest access + account linking verified by PowMCP
VS CodeOpen VS Code setup Guest access available · Account linking not yet verified
KiroOpen Kiro setup Guest access available · Account linking not yet verified
LM StudioOpen LM Studio setup Guest access available · Account linking not yet verified
Visual StudioOpen Visual Studio setup (Windows) Guest access available · Account linking not yet verifiedCopy one ready-to-send prompt for any agent that supports remote MCP connections.
For clients that require manual configuration, use this app-only endpoint, its JSON entry, or one terminal command.
ChatGPT: enable Developer mode in Settings → Security and login, then add this MCP endpoint from the Plugins page. Availability depends on your account and workspace policy. PowMCP has not yet verified ChatGPT account linking. OpenAI setup guide
https://powmcp.com/netcdf-cf-check/mcp {
"mcpServers": {
"powmcp-netcdf-cf-check": {
"type": "http",
"url": "https://powmcp.com/netcdf-cf-check/mcp"
}
}
}Terminal agents add this app with one command:
claude mcp add --transport http powmcp-netcdf-cf-check https://powmcp.com/netcdf-cf-check/mcpcodex mcp add powmcp-netcdf-cf-check --url https://powmcp.com/netcdf-cf-check/mcpgemini mcp add --transport http powmcp-netcdf-cf-check https://powmcp.com/netcdf-cf-check/mcpManage, disable, or remove this connection in your agent's own MCP settings. PowMCP does not label an external connection as installed without confirmation from that client.
Proof
Check a hosted netCDF file against the CF Metadata Conventions from a public URL, with per-check rule evidence and no upload
Validate one public netCDF file against the CF (Climate & Forecast) Metadata Conventions (optionally the ACDD and IOOS suites) with per-check section, severity, and variable/attribute evidence, or compare two same-lineage files, keeping metadata conformance strictly separate from scientific data correctness.
Request cost1 completed result
Guests get 50 lifetime app requests. Free accounts get 100 each calendar month.
cf_check
Validates one directly hosted public netCDF file (a .nc file or a netCDF-serving OPeNDAP/ERDDAP/THREDDS endpoint, fetched over HTTP(S) under a ~256 MB cap and magic-confirmed as CDF classic netCDF-3 or \x89HDF netCDF-4/HDF5) against the CF (Climate & Forecast) Metadata Conventions (optionally the ACDD and IOOS suites) run fully offline by the pinned IOOS compliance-checker 6.1.0 in a no-network sandbox. Returns overall pass, per-suite scored points (e.g. 128/133) and versions, per-check results by CF section (e.g. §2.5, §4.4) with severity (high/medium/low) and state (check-passed, check-failed, check-not-applicable) and the engine messages, severityCounts, the declared Conventions attribute, a structural inventory (dimensions, variables, global attributes), and distinguished states (not-netcdf vs netcdf-unreadable). Use for one-file conformance and fix-my-metadata questions: 'does this file conform to CF', 'which attributes fail', 'is it ready to archive to NCEI/ESGF/THREDDS'. A pass means only that the metadata satisfied the automated CF (or ACDD/IOOS) ruleset at compliance-checker 6.1.0 (never that the scientific data values are correct, calibrated, physically valid, or publication-ready, so humanReviewRequired is always true), and it does not validate an unhosted local file. Downloads a multi-megabyte binary then validates it; the engine is sub-second but the download can take up to ~90 seconds. Tell the user before calling. Never repeat netCDF URL query strings in narration.
cf_compare
Runs the identical pinned IOOS compliance-checker 6.1.0 validation against exactly two directly hosted public netCDF files of the SAME dataset lineage (the same canonical resource across revisions; the declared CF/Conventions version may differ), baseline first, revised second, sequentially under one shared 115-second deadline, then reports which CF (and optionally ACDD/IOOS) checks regressed or were resolved by section. Select this whenever two netCDF URLs are given and the user asks what conformance changed between revisions or which file has fewer machine-checkable metadata findings; the tool assesses lineage itself and flags the pair not-comparable (still reporting the raw section diff) when the files do not line up, so you do not need to pre-verify sameness. Returns per-file hashes, models, declared conventions, pass verdicts and severityCounts; a comparability note; a difference table of checks introduced (regressions) and resolved keyed by suite and section; and a ranking by pass state then fewer failed high-severity checks. The ranking orders automated metadata conformance only (it never means one file's data is truer, better calibrated, or higher quality), and human review remains required for both. Downloads and validates two live files and can take up to ~90 seconds. Tell the user before calling. Never repeat netCDF URL query strings in narration.
Other apps for the jobs next to netCDF CF Check.
Scope and boundaries for netCDF CF Check.
Check the pinned xarray air-temperature sample with CF and normal criteria to inspect real metadata findings. The comparison uses the same dataset before and after its filename-only rename: this is a no-change control, with zero metadata regressions expected. Replace the URLs with your own dataset revisions to investigate actual changes; add ACDD or IOOS only when required.
Read netcdfState before pass. For a validated netCDF file, pass means every selected suite passed at the selected criteria; fix failed checks from high to low severity using their CF section and engine messages. In comparisons, call differences revision regressions only when comparable is true; otherwise they are a raw check difference, and truncation means the table can be incomplete.
Inputs must be public netCDF files or netCDF-serving OPeNDAP, ERDDAP, or THREDDS endpoints under the fetch cap; unhosted local files are not checked. Passing CF, ACDD, or IOOS metadata rules does not verify scientific values, calibration, physical validity, or publication readiness, so human review remains required.