Grandline Mcp

io.github.luzomiPublished by GitHub account luzomiv0.2.2Updated Oct 24, 2026

Empirical maritime distances from real AIS tracks: 4 route variants, port lookup, bulk matrix

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

A local MCP server that gives an assistant empirical maritime distances and routes derived from real AIS vessel tracks, plus port lookup and bulk matrices.

What you can do
Look up ports and obtain empirical maritime distances between them, based on real AIS tracks rather than theoretical great-circle lines. Choose among four route variants when computing a route. Compute bulk distance matrices for many port pairs at once. Point the client at an alternative API base URL if needed.
When to use it
Useful when an assistant needs shipping or sailing distances between ports for logistics, routing or analysis, and a realistic track-based figure matters more than a straight-line estimate.
Requirements
Runs as a local Python package (grandline-mcp) over stdio on a desktop machine. An API key in GRANDLINE_API_KEY is optional; without it the anonymous tier allows 5 calls total per IP. GRANDLINE_API_URL can override the default API base URL. Network access to the Grandline API is required.
Before you install
The API key is a bearer token obtained from the provider's registration page; keep it private. Without a key usage is capped at 5 calls per IP, so heavier use needs an account. Queries are sent to the third-party Grandline API, and overriding GRANDLINE_API_URL sends them to whatever endpoint is set.

Installation

In SourceWeft

  1. Open Grandline Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.