io.github.mayurrawte/searoute
NPM · @SEAROUTE-TS/MCP · SCANNED SEP 21
Real shortest sea routes between ports: distance, canals/straits, GeoJSON. UN/LOCODE aware.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 502 tokens (~251/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 Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
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
How do I install the io.github.mayurrawte/searoute MCP server?
io.github.mayurrawte/searoute runs locally as an npm package, launched with npx -y @searoute-ts/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @searoute-ts/mcp
claude mcp add mayurrawte-searoute -- npx -y @searoute-ts/mcp
{
"mcpServers": {
"mayurrawte-searoute": {
"command": "npx",
"args": [
"-y",
"@searoute-ts/mcp"
]
}
}
} {
"servers": {
"mayurrawte-searoute": {
"command": "npx",
"args": [
"-y",
"@searoute-ts/mcp"
]
}
}
} codex mcp add mayurrawte-searoute -- npx -y @searoute-ts/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mayurrawte-searoute": {
"type": "local",
"command": [
"npx",
"-y",
"@searoute-ts/mcp"
],
"enabled": true
}
}
} openclaw mcp add mayurrawte-searoute --command npx --arg -y --arg @searoute-ts/mcp
mcp_servers:
mayurrawte-searoute:
command: "npx"
args: ["-y", "@searoute-ts/mcp"] {
"McpServers": {
"mayurrawte-searoute": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@searoute-ts/mcp"
]
}
}
} assistant mcp add mayurrawte-searoute -t stdio -c npx -a -y @searoute-ts/mcp
{
"mcpServers": {
"mayurrawte-searoute": {
"command": "npx",
"args": [
"-y",
"@searoute-ts/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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +4
- Stability: unverified → 0.30 ▲ functional
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 21 Sept 2026 · Analysed npm/@searoute-ts/mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 32 |
| 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 →
sea_route Shortest sea route ~268
Compute the shortest maritime route between two points (UN/LOCODE port codes like "CNSHA", or [lon, lat] coordinates). Returns distance, optional duration, the canals/straits traversed, and the route GeoJSON. Supports passage restrictions (e.g. avoid Suez), arctic gating, and vessel-draft-aware canal avoidance.
| Name | Type | Req | Description |
|---|---|---|---|
| allowArctic | boolean | – | Allow the ice-blocked Northwest/Northeast Passages (blocked by default). |
| destination | – | yes | – |
| includeGeometry | boolean | – | Include the route LineString GeoJSON in the result. |
| maxSnapDistanceKm | number | – | Reject inputs farther than this (km) from the maritime network. |
| origin | – | yes | A UN/LOCODE port code string, or a [longitude, latitude] coordinate pair. |
| restrictions | array | – | Named passages the route must avoid. e.g. ["suez","babelmandeb"] forces Cape of Good Hope routing during a Red Sea disruption. |
| speedKnots | number | – | Vessel speed in knots; when given, an estimated duration in hours is returned. |
| units | string | – | Unit for the returned distance. |
| vesselDraftMeters | number | – | Vessel draft in metres; canals too shallow for it are auto-avoided. |
No output schema declared.
No examples provided.
sea_route_alternatives Alternative sea routes ~234
Return up to k distinct alternative maritime routes between two points, each blocking a different combination of major canals/straits (e.g. baseline vs. no-Suez vs. no-Panama), sorted by distance. Useful for comparing "via Suez" against "via Cape of Good Hope".
| Name | Type | Req | Description |
|---|---|---|---|
| allowArctic | boolean | – | Allow the ice-blocked Northwest/Northeast Passages (blocked by default). |
| destination | – | yes | – |
| includeGeometry | boolean | – | Include each route LineString GeoJSON in the result (off by default; verbose). |
| k | integer | – | Maximum number of distinct alternative routes to return. |
| origin | – | yes | A UN/LOCODE port code string, or a [longitude, latitude] coordinate pair. |
| restrictions | array | – | Named passages the route must avoid. e.g. ["suez","babelmandeb"] forces Cape of Good Hope routing during a Red Sea disruption. |
| units | string | – | Unit for the returned distance. |
| vesselDraftMeters | number | – | Vessel draft in metres; canals too shallow for it are auto-avoided. |
No output schema declared.
No examples provided.
What is the io.github.mayurrawte/searoute MCP server?
io.github.mayurrawte/searoute is an MCP server listed in the public MCP registry as io.github.mayurrawte/searoute. Real shortest sea routes between ports: distance, canals/straits, GeoJSON. UN/LOCODE aware. This page covers its npm package (@searoute-ts/mcp).
Is the io.github.mayurrawte/searoute MCP server safe to use?
io.github.mayurrawte/searoute scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.mayurrawte/searoute MCP server expose?
io.github.mayurrawte/searoute exposes 2 tools: sea_route, sea_route_alternatives. Their descriptions and schemas cost roughly 502 tokens of context every time the server is loaded.
Is the io.github.mayurrawte/searoute MCP server still maintained?
io.github.mayurrawte/searoute is still listed as active in the MCP registry. We last reached this channel on 21 September 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 io.github.mayurrawte/searoute MCP server under?
io.github.mayurrawte/searoute declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.