shipfinder

View descriptor → ShipFinder AIS Data API provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

⚠ Proposed MCP surface. No official hosted MCP server was found for ShipFinder AIS Data API. The tools below are a candidate set derived from this provider's API, and the link points at the source descriptor rather than a live server. If ShipFinder AIS Data API publishes an official server, this page will update to it on the next build.

Provider: ShipFinder AIS Data API Type: Candidate descriptor Transport: Host: raw.githubusercontent.com

Descriptor

https://raw.githubusercontent.com/api-evangelist/shipfinder-ais-data-api/refs/heads/main/mcp/shipfinder-ais-data-api-mcp.yml

Candidate descriptor · transport

Tools

get_fleet_position — 1.1.3 Fleet Position
get_vessel_flag_info — 1.5 Vessel Flag Information
get_vessel_position_multi — 1.1.2 Multi-vessel Position
get_vessel_position_single — 1.1.1 Single Vessel Position
get_vessel_search — 1.2 Vessel Search
get_vessels_in_zone — 1.4 Vessels in Zone
get_vessels_nearby — 1.3 Vessels Nearby
post_add_fleet — 7.1.1 Create Fleet
post_add_geofence — 7.2.1 Geofence Creation
post_add_vessel_speed_alert — 7.3.1 Add Vessel Speed Alert Subscription
post_add_vessel_to_fleet — 7.1.5 Add Vessels to Fleet
post_delete_fleet — 7.1.4 Delete Fleet
post_delete_fleet_vessel — 7.1.7 Remove Vessels from Fleet
delete_geofence — 7.2.4 Geofence Deletion
post_delete_vessel_speed_alert — 7.3.2 Delete Vessel Speed Alert Subscription
get_fleet — 7.1.3 Query Fleet
get_geofence — 7.2.3 Geofence Query
post_update_fleet_info — 7.1.2 Update Fleet Information
post_update_fleet_vessel — 7.1.6 Batch Update Vessels in Fleet
post_update_geofence — 7.2.2 Geofence Update
get_vessel_speed_alert_list — 7.3.3 Query Vessel Speed Alert Subscription List
get_port_call_records_by_port — 3.6 Port Calls Records for Port
get_port_call_records_by_vessel — 3.3 Vessel Port Call History
get_port_call_records_by_vessel_at_port — 3.4 Vessel Port Call Records at Specific Port
get_vessel_current_port_call — 3.5 Vessel Current Port Call
get_vessel_history_track — 3.1 Vessel History Track
get_vessel_sts_events — 3.2 Ship-to-Ship (STS) Events
get_cyclone_info — 5.1.2 Tropical Cyclone Details by Point
get_cyclones_list — 5.1.1 Global Tropical Cyclones List
get_marine_weather — 5.3 Global Marine Weather
get_tide_station_info — 5.2.2 Query Single Tide Gauge Station Details
get_tide_station_list — 5.2.1 Request parameters for Global Tide Gauge Stations List
get_e_t_a — 4.3 ETA Query
get_route_plan_point_to_point — 4.1 Point-to-Point Route Planning
get_route_plan_port_to_port — 4.2 Port-to-Port Route Planning
get_port_anchored_vessels — 2.3 Currently Anchored Vessels
get_port_berthed_vessels — 2.2 Currently Berthed Vessels
get_port_expected_arrivals — 2.4 Inbound / Expected Arrivals
get_port_info — 2.1 Port Information
get_navigational_warnings — 6.1 China Region Navigational Warnings

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.