# io.github.mayurrawte/searoute (npm · @searoute-ts/mcp)

Real shortest sea routes between ports: distance, canals/straits, GeoJSON. UN/LOCODE aware.

- Trust score: 78/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `@searoute-ts/mcp`: 78/100 (this document), [markdown](https://verifymcp.io/servers/mayurrawte-searoute/searoute-ts-mcp.md), [page](https://verifymcp.io/servers/mayurrawte-searoute/searoute-ts-mcp)

## Channel facts

- Registry: `npm`
- Package: `@searoute-ts/mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 32 of 114 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add mayurrawte-searoute -- npx -y @searoute-ts/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mayurrawte-searoute": {
      "command": "npx",
      "args": [
        "-y",
        "@searoute-ts/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mayurrawte-searoute": {
      "command": "npx",
      "args": [
        "-y",
        "@searoute-ts/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mayurrawte-searoute -- npx -y @searoute-ts/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mayurrawte-searoute": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@searoute-ts/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mayurrawte-searoute --command npx --arg -y --arg @searoute-ts/mcp
```

### Hermes

```yaml
mcp_servers:
  mayurrawte-searoute:
    command: "npx"
    args: ["-y", "@searoute-ts/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mayurrawte-searoute": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@searoute-ts/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mayurrawte-searoute -t stdio -c npx -a -y @searoute-ts/mcp
```

### Other

```json
{
  "mcpServers": {
    "mayurrawte-searoute": {
      "command": "npx",
      "args": [
        "-y",
        "@searoute-ts/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 78, +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.

### 2026-09-19 (score 77, +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.

### 2026-09-17 (score 76, +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.

### 2026-09-15 (score 75, +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.

### 2026-09-13 (score 74, +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.

### 2026-09-11 (score 73, +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.

### 2026-09-08 (score 72, +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.

### 2026-09-07 (score 71, +4)

- [functional improvement] Stability: unverified → 0.30

## MCP tools (2)

### `sea_route` (~268 tokens)

Shortest sea route

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.

Input parameters:

- `allowArctic` (boolean): Allow the ice-blocked Northwest/Northeast Passages (blocked by default).
- `destination` (required)
- `includeGeometry` (boolean): Include the route LineString GeoJSON in the result.
- `maxSnapDistanceKm` (number): Reject inputs farther than this (km) from the maritime network.
- `origin` (required): 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.

### `sea_route_alternatives` (~234 tokens)

Alternative sea routes

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

Input parameters:

- `allowArctic` (boolean): Allow the ice-blocked Northwest/Northeast Passages (blocked by default).
- `destination` (required)
- `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` (required): 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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mayurrawte-searoute/searoute-ts-mcp#diagnostics

## Score history

- 2026-09-21: 78
- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 72
- 2026-09-07: 71
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 67
- 2026-09-03: 67
- 2026-09-02: 67
- 2026-09-01: 67
- 2026-08-31: 67
- 2026-08-30: 67
- 2026-08-29: 52

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/@searoute-ts/mcp
- Socket report: https://socket.dev/npm/package/@searoute-ts/mcp
- Repository: https://github.com/mayurrawte/searoute-ts
- Changelog RSS feed: https://verifymcp.io/servers/mayurrawte-searoute/searoute-ts-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mayurrawte-searoute/searoute-ts-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mayurrawte-searoute/searoute-ts-mcp