ais_vessels_near
Pack: digitraffic-ais · Endpoint: https://gateway.pipeworx.io/digitraffic-ais/mcp
Live vessel positions near a point: which ships are in the water around a location right now, from AIS vessel tracking. Returns per ship the MMSI, vessel name, ship type (cargo, tanker, passenger ferry, fishing, tug, sailing, pleasure craft, military), speed in knots, course, navigational status (under way, at anchor, moored, fishing), lat/lon, distance from the centre, and how fresh the report is. Use for “what ships are near Helsinki”, “vessel traffic outside Turku”, “is anything anchored off this port”, “boats in the Gulf of Finland”. COVERAGE IS REGIONAL: Fintraffic AIS receivers cover Finland and the surrounding Baltic Sea (Gulf of Finland, Gulf of Bothnia, Archipelago Sea, Åland, fringe reception toward Estonia and Sweden). Points elsewhere in the world return nothing. Example: latitude 60.15, longitude 24.95, radius_km 50 for Helsinki; add vessel_type “tanker” to see only tankers.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
latitude | number | yes | Centre latitude in decimal degrees, e.g. 60.15 for Helsinki. |
longitude | number | yes | Centre longitude in decimal degrees, e.g. 24.95 for Helsinki. |
radius_km | number | no | Search radius in kilometres. Default 25, maximum 100. |
vessel_type | string | no | Optional ship-type filter. One of: cargo, tanker, passenger, ferry, cruise, fishing, tug, towing, pilot, sar, military, sailing, pleasure, yacht, law enforcement, dredging, high-speed, service, other. |
limit | number | no | Maximum vessels to return, nearest first. Default 50, maximum 200. |
Example call
curl -X POST https://gateway.pipeworx.io/digitraffic-ais/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ais_vessels_near","arguments":{}}}'Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"digitraffic-ais": {
"url": "https://gateway.pipeworx.io/digitraffic-ais/mcp"
}
}
}See Getting Started for client-specific install steps.