VDatum MCP Server
PYPI · VDATUM-MCP
MCP server for vertical datum conversions using coastalmodeling-vdatum
Available components
Last scanned (1 day ago)
Scores higher than 91% of PyPI servers
Category Maps and Location
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 30 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency74
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to mansurjisan/ocean-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 98 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 326 tokens (~163/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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.
- 30 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 29 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 18 Oct 26 −15
- Malware scan: pass → unverified ▼ security
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 Nov 2026 · Analysed pypi/vdatum-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 | mansurjisan/ocean-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mansurjisan/ocean-mcp/.github/workflows/publish.yml@refs/tags/vdatum-mcp-v0.1.1 |
| Rekor log index | 2276064874 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:e264a67a6ea263404e2cc6e17d374926dc6c8d62d2318e64c011d4eafc3489d5 |
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 30 packages
| Packages resolved | 30 |
|---|---|
| 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 →
vdatum_convert ~297
Convert elevation values between vertical datums. Supports conversions between NAVD88, MLLW, MLW, MHW, MHHW, LMSL, xGEOID20b, IGLD85, and LWD using NOAA's coastalmodeling-vdatum. Points outside the datum conversion domain return inf. Args: datum_from: Source vertical datum (e.g. 'navd88', 'mllw'). datum_to: Target vertical datum (e.g. 'mllw', 'navd88'). lat: Latitude(s) as comma-separated values or single value (e.g. '30.0' or '30.0,26.0,27.5'). lon: Longitude(s) as comma-separated values or single value (e.g. '-80.0' or '-80.0,-75.0,-77.5'). z: Elevation(s) in meters as comma-separated values or single value (e.g. '1.5' or '1.5,0.0,0.1'). online: If true (default), fetch geotiff grids from AWS. Set false for offline/HPC use.
| Name | Type | Req | Description |
|---|---|---|---|
| datum_from | string | yes | – |
| datum_to | string | yes | – |
| lat | string | yes | – |
| lon | string | yes | – |
| online | boolean | – | – |
| z | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
vdatum_list_datums ~29
List all supported vertical datums for conversion. Shows each datum's abbreviation and full name.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the VDatum MCP Server server?
VDatum MCP Server runs locally as a PyPI package, launched with uvx vdatum-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 · vdatum-mcp
claude mcp add mansurjisan-vdatum-mcp -- uvx vdatum-mcp
What is the VDatum MCP Server server?
VDatum MCP Server is listed in the public MCP registry as io.github.mansurjisan/vdatum-mcp. MCP server for vertical datum conversions using coastalmodeling-vdatum. This page covers its PyPI package (vdatum-mcp).
Is the VDatum MCP Server server safe to use?
VDatum MCP Server scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 VDatum MCP Server server expose?
VDatum MCP Server exposes 2 tools: vdatum_convert, vdatum_list_datums. Their descriptions and schemas cost roughly 326 tokens of context every time the server is loaded.
Is the VDatum MCP Server server still maintained?
VDatum MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 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 VDatum MCP Server server under?
VDatum 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.