Japan Port Vessel Traffic MCP (AIS Position & ETA)

io.github.atushi1841Published by GitHub account atushi1841v0.1.0Updated Nov 2, 2026

Port vessel traffic MCP Apify apify.com/fruitful_quintessence Gumroad atushi5.gumroad.com/l/kutuxe

The publisher's own server: Port

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Local MCP server that gives an assistant live AIS vessel positions, tracks and ETA estimates for 20 major Japanese ports.

What you can do
  • List the 20 pre-configured Japanese ports with their bounding boxes
  • Look up live vessels inside a port and fetch a single vessel's latest position and static details
  • Retrieve historical vessel tracks as GeoJSON coordinates
  • Estimate ETA and delay by comparing AIS-reported and speed-projected arrival
  • Summarize port activity by vessel type, flag and status
When to use it
Useful when you want an assistant to answer questions about ship traffic in Japanese ports — which vessels are in port, where a ship is, its recent track, or whether it is running late — without signing up for a commercial AIS feed.
Requirements
Runs as a local stdio process; the README installs it from the repository with uv (or pip) and starts it via uv run. No API key is declared for the anonymous tier, and no environment variables or headers are declared. Network access to the Open Waters AIS API is needed.
Before you install
Data comes from an aggregate of community AIS receivers, AISHub and aisstream, so coverage and accuracy are not official or guaranteed. Requests go to a third-party AIS API. The README also points to paid Apify and Gumroad listings, which are separate from this local server.

Installation

In SourceWeft

  1. Open Japan Port Vessel Traffic MCP (AIS Position & ETA) 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

Japan Port Vessel Traffic MCP

OpenWaters AIS ベースの日本港湾船舶交通データ MCP サーバー。 API キー不要・完全無料・公開 AIS データ(tosa compliant)。

Features

  • 20 major Japanese ports pre-configured with bounding boxes
  • Real-time vessel position, name, IMO, flag, destination, ETA
  • Historical track (up to 366 days)
  • ETA & delay estimation (AIS-reported vs speed-projected)
  • Port overview aggregation (counts by type, flag, status)

Data source

Open Waters AIS — aggregate of community AIS receivers, AISHub, aisstream. No official API key required for the anonymous tier. Source: https://ais.openwaters.io/api/ais/

Installation

bash
git clone https://github.com/atushi1841/japan-port-vessel-mcp.gitcd japan-port-vessel-mcpuv sync  # or: pip install -r requirements.txt

Usage (stdio)

bash
uv run --directory . src/stdio_main.py

Or configure in Claude Desktop / Cursor MCP settings:

json
{  "mcpServers": {    "japan-port-vessel": {      "command": "uv",      "args": ["run", "--directory", "<path-to-repo>", "src/stdio_main.py"]    }  }}

Tools

ToolDescription
list_japan_ports()Catalog of 20 Japanese ports with bboxes
get_vessels_in_port(port_code, limit=30)Live vessel list within a port bbox
get_vessel(mmsi)Single-vessel latest position + static info
get_vessel_track(mmsi, hours=24, interval="5m", limit=500)Historical track as GeoJSON coordinates
estimate_vessel_eta(mmsi, port_code=None)ETA delay estimation
get_port_overview(port_code, max_age_hours=6)Aggregated port activity summary

Quick examples

python
# List Japanese portsports = list_japan_ports()
# Vessels in Tokyo Baytokyo = get_vessels_in_port("JPTYO", limit=20)
# ETA delay for a specific vesseleta = estimate_vessel_eta("431005321", port_code="JPTYO")print(eta["delay_hours"])

License

MIT — like the Open Waters AIS network. Attribution required.

Related

Apify Store

This MCP server is published as an Apify Actor: japan-port-vessel-mcp.

Apify Store: atushi1841


Data & Store

Source: README.md at commit 0d91d41

Tools

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

Version history

1
  1. v0.1.0LatestOct 18, 2026

Score

40% 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Port integrations