Japan Port Vessel Traffic MCP (AIS Position & ETA)
Port vessel traffic MCP Apify apify.com/fruitful_quintessence Gumroad atushi5.gumroad.com/l/kutuxe
What can you do with Japan Port Vessel Traffic MCP (AIS Position & ETA)?
- 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)
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
https://github.com/atushi1841/japan-port-vessel-mcp/releases/download/v0.1.0/server.mcpbDocumentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
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
git clone https://github.com/atushi1841/japan-port-vessel-mcp.git
cd japan-port-vessel-mcp
uv sync # or: pip install -r requirements.txt
Usage (stdio)
uv run --directory . src/stdio_main.py
Or configure in Claude Desktop / Cursor MCP settings:
{
"mcpServers": {
"japan-port-vessel": {
"command": "uv",
"args": ["run", "--directory", "<path-to-repo>", "src/stdio_main.py"]
}
}
}
Tools
| Tool | Description |
|---|---|
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
# List Japanese ports
ports = list_japan_ports()
# Vessels in Tokyo Bay
tokyo = get_vessels_in_port("JPTYO", limit=20)
# ETA delay for a specific vessel
eta = estimate_vessel_eta("431005321", port_code="JPTYO")
print(eta["delay_hours"])
License
MIT — like the Open Waters AIS network. Attribution required.
Related
- OpenWaters AIS API: https://ais.openwaters.io/api/ais/
Apify Store
This MCP server is published as an Apify Actor: japan-port-vessel-mcp.
Apify Store: atushi1841
Data & Store
- Apify Store: https://apify.com/fruitful_quintessence
- Gumroad datasets: https://atushi5.gumroad.com/l/kutuxe
Frequently asked questions
What is Japan Port Vessel Traffic MCP (AIS Position & ETA)?
Port vessel traffic MCP Apify apify.com/fruitful_quintessence Gumroad atushi5.gumroad.com/l/kutuxe
How do I install Japan Port Vessel Traffic MCP (AIS Position & ETA)?
Follow the installation steps in its documentation, shown on this page and in its repository.
Does Japan Port Vessel Traffic MCP (AIS Position & ETA) need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Japan Port Vessel Traffic MCP (AIS Position & ETA) open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains Japan Port Vessel Traffic MCP (AIS Position & ETA)?
It is published by atushi1841. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.