Searoute

Created By
Project-Harrison8 months ago
A Maritime Routing MCP Server that computes sea routes and geodesic distances using searoute and geopy. Built for maritime operations and research.
Overview

what is Searoute?

Searoute is a Maritime Routing MCP Server that computes sea routes and geodesic distances using searoute and geopy, designed for maritime operations and research.

how to use Searoute?

To use Searoute, input simple latitude and longitude coordinates to compute oceangoing distances and generate full sea routes with waypoints in GeoJSON format.

key features of Searoute?

  • Computes sea routes with waypoints
  • Calculates geodesic great-circle distances
  • Integrates with Model Context Protocol (MCP) for LLM clients

use cases of Searoute?

  1. Planning maritime logistics and transportation routes
  2. Researching oceanic distances for navigation
  3. Comparing different routing options for efficiency

FAQ from Searoute?

  • Can Searoute handle all maritime routing needs?

Yes! Searoute is built to handle various maritime routing scenarios and can compute distances and routes effectively.

  • Is Searoute open-source?

Yes! Searoute is available on GitHub for public use and contributions.

  • How accurate are the distance calculations?

Searoute uses geodesic calculations to ensure high accuracy in distance measurements.

Server Config

{
  "mcpServers": {
    "searoute_mcp": {
      "command": "searoute-mcp",
      "args": [],
      "env": {}
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
Project-Harrison
Star
-
Language
-
License
-

Recommend Servers

View All
Alloy

2 days ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

12 hours ago
Crevio

a day ago