4,500+ servers built on MCP Fusion
Vinkius

VesselAPI MCP. Track ships and audit global port schedules instantly.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

VesselAPI MCP on Cursor AI Code Editor MCP Client VesselAPI MCP on Claude Desktop App MCP Integration VesselAPI MCP on OpenAI Agents SDK MCP Compatible VesselAPI MCP on Visual Studio Code MCP Extension Client VesselAPI MCP on GitHub Copilot AI Agent MCP Integration VesselAPI MCP on Google Gemini AI MCP Integration VesselAPI MCP on Lovable AI Development MCP Client VesselAPI MCP on Mistral AI Agents MCP Compatible VesselAPI MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

VesselAPI tracks maritime vessels and global ports using specific tools. Your agent reads current AIS positions, audits future port schedules, or retrieves detailed specs for any ship by IMO number.

It’s a single connection point to all global shipping data.

What your AI agents can do

Check api status

Confirms if the VesselAPI service is currently running and available for querying.

Get vessel details

Retrieves specific metadata on a vessel, requiring only its IMO number as input.

Get vessel position

Gets the most recent AIS coordinates for any specified ship to track its current location.

+ 3 more capabilities included
Check System Status

Confirm if the API connection is active and ready to pull vessel data.

Get Vessel Details by IMO

Retrieve deep specs on any ship, including its flag, type, and build information, using only its IMO number.

Find Current Position

Fetch the most recent AIS coordinates to pinpoint a vessel's location globally.

Audit Port Schedules

Look up upcoming and historical port calls for a specific ship, mapping out its expected journey.

List Global Ports

Pull a list of all supported maritime ports worldwide to guide geographic planning.

Search by Name

Narrow down the vessel pool by searching for ships using their known name.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

VesselAPI MCP Server: 6 Tools for Maritime Data Retrieval

Use these six tools to query vessel status, retrieve current AIS coordinates, audit port schedules, and list global maritime ports via your AI agent.

check019d8498

check api status

Confirms if the VesselAPI service is currently running and available for querying.

get019d8498

get vessel details

Retrieves specific metadata on a vessel, requiring only its IMO number as input.

get019d8498

get vessel position

Gets the most recent AIS coordinates for any specified ship to track its current location.

get019d8498

get vessel schedules

Lists a vessel's upcoming and past port calls, giving a view of its itinerary.

list019d8498

list maritime ports

Provides an exhaustive list of all global ports supported by the API for planning purposes.

search019d8498

search vessels

Finds vessels using a simple name search, helping you narrow down your target IMO number.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with VesselAPI, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

VesselAPI gives your agent a direct line into global maritime data. Forget jumping between half-baked dashboards or running separate API calls for every little piece of info you need. You connect this server, and it hands your AI client access to the whole playbook for tracking ships and checking out international ports.

Your agent handles complex logistics questions in natural language—it’s one single point of connection to all global shipping intelligence.

To get started, your first call needs to be check_api_status. This confirms if the entire VesselAPI service is up and running; you need to know the feed is live before you try pulling any data.

If you're tracking a specific vessel, the process starts with finding it or getting its specs. You can use search_vessels when you only have a name—this tool helps you narrow down the pool of ships until your agent finds the precise IMO number you need. Once you’ve got that ID, you pull deep metadata using get_vessel_details.

This retrieves crucial specifications on the ship, including its flag, type, and build history.

For real-time tracking, you call get_vessel_position, which pulls the most recent AIS coordinates. You instantly pinpoint a vessel's current location anywhere in the world. To map out the whole trip, use get_vessel_schedules. This tool lists both upcoming and historical port calls, giving your agent a full view of where the ship has been and where it’s headed next.

For broader planning, you can pull comprehensive data using two other tools. First, if you need to know what ports are even available for transshipment or docking, list_maritime_ports provides an exhaustive list of every global port supported by the API. Second, while searching for a vessel's specific itinerary, your agent also handles finding its general details and current coordinates from one query set.

Your agent doesn't just pull random facts; it stitches them together. You can ask if a ship currently at X coordinates has a scheduled port call in Y weeks, or you can check the specs of every vessel flagged under Z country. It’s all connected through these tools: check_api_status verifies service availability; search_vessels finds ships by name; get_vessel_details provides deep technical metadata using an IMO number; get_vessel_position gives real-time AIS coordinates; get_vessel_schedules maps out the entire port calling itinerary (both past and future); and finally, list_maritime_ports supplies a comprehensive directory of every supported global port.

You’ll stop asking your agent to switch connections because it handles all this data—location, specs, and logistics—in one go.

How VesselAPI MCP Works

  1. 1 Subscribe to the server and enter your unique VesselAPI Key into your AI client.
  2. 2 Ask your agent a specific question (e.g., 'Where is IMO 9411159 right now?').
  3. 3 The agent executes the necessary tool call, pulls the data, and presents the answer in plain language.

The bottom line is: you talk to your agent, it talks to VesselAPI, and you get the live shipping data back.

Who Is VesselAPI MCP For?

Supply Chain Analysts who hate clicking through multiple tracking portals. Trade Researchers stuck verifying port history manually. Logistics Managers needing rapid audits of ship positions during a crisis. If your job involves knowing where a shipment is right now, this is for you.

Logistics Manager

Uses the agent to perform rapid position checks (get_vessel_position) across multiple vessels simultaneously when delays pop up.

Supply Chain Analyst

Runs audits on vessel specs (get_vessel_details) and schedules (get_vessel_schedules) to verify if a shipment will hit its deadline.

Trade Researcher

Uses list_maritime_ports to map out potential trade routes and then checks specific vessels against those ports.

What Changes When You Connect

  • Get real-time location data immediately. Instead of viewing a static dashboard, your agent runs get_vessel_position to tell you exactly where the vessel is right now.
  • Build comprehensive profiles fast. Use get_vessel_details with just an IMO number to get specs like flag and type—no manual lookups needed.
  • Plan around port stops efficiently. Run get_vessel_schedules to see a ship's entire itinerary, including future expected arrival dates at Rotterdam or Shanghai.
  • Start broad, then narrow down. If you don't have the IMO number, use search_vessels first. It finds the vessel by name so you can run detailed checks later.
  • Map out potential routes globally. Use list_maritime_ports to generate a master list of global docking points for planning and comparison.

Real-World Use Cases

01

Auditing an overdue shipment

A logistics manager needs to know why Container Ship 'MSC OSCAR' is delayed. Instead of checking three different tracking sites, they ask their agent: 'What are the schedules for MSC OSCAR and where is it now?' The agent runs get_vessel_schedules (checking past/future stops) and then immediately follows up with get_vessel_position, giving a full picture in one response.

02

Mapping out new trade routes

A trade researcher needs to see all potential ports between Miami and Panama. They first run list_maritime_ports to get the list, then use that data structure to verify if a specific vessel (found via search_vessels) is calling at any of those listed ports.

03

Verifying cargo specs

A supply chain analyst receives an IMO number and needs assurance it's the right ship. They first call get_vessel_details to confirm the type (e.g., Container Ship) and flag, then use that knowledge to check its current position with get_vessel_position.

04

Checking for scheduling conflicts

An operations lead needs to know if a ship is on track. They ask their agent: 'Show me the schedules for IMO 9243394.' The agent runs get_vessel_schedules and can immediately identify potential gaps or deviations from the planned stops.

The Tradeoffs

Trying to manually copy IDs

A user finds a vessel name on one page, copies it, pastes it into another tool's input field, and hopes it works. This fails because the tools require specific identifiers like IMO numbers or exact port names.

Always let your agent orchestrate this. If you only have a name, first run search_vessels to get the correct ID, then feed that output directly into get_vessel_position.

Assuming data consistency

A user assumes that because they checked the status with check_api_status, all subsequent calls will work without issue. This ignores potential rate limits or authentication failures.

Treat every tool call as its own step. Check the API status first, and if you get an error on a specific data point (like position), try running get_vessel_details to see if that information is available instead.

Over-relying on search

Only searching by name using search_vessels. This only gives a general idea and doesn't confirm the vessel’s current activity or actual specs.

Use search_vessels to get candidates, but always follow up with get_vessel_position to validate the real-time location. Name is never enough.

When It Fits, When It Doesn't

Use this if your core need is tracking movement or verifying structured data points (IMO details, coordinates, scheduled dates). You're looking for 'where' or 'when.' Don't use it if you just want general market intelligence about shipping tariffs or cargo capacity—those require different types of tools. If all you have is a vessel name and no ID, start with search_vessels. Once you have the IMO number, your options expand drastically: run get_vessel_details for specs, get_vessel_position for where it is now, or get_vessel_schedules for its plan. If you're just mapping potential destinations, stick to list_maritime_ports. This server handles the 'who,' 'what,' and 'where.'

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by VesselAPI. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 6 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

check_api_status get_vessel_details get_vessel_position get_vessel_schedules list_maritime_ports search_vessels

Checking a ship's location shouldn't require jumping between three different APIs.

Today, checking on one vessel means opening your primary tracking dashboard, then logging into the port authority site for schedules, and finally hitting an external AIS data portal just to see coordinates. You spend more time clicking tabs and copy-pasting IDs than you do analyzing the movement.

With VesselAPI, you ask your agent one simple question—like 'What's the status of IMO 9411159?' Your agent runs all the necessary checks behind the scenes, pulling live data on position, specs, and schedules into a single, coherent answer. You just get the answer.

VesselAPI MCP Server: Get accurate maritime intelligence.

The manual steps that go away are cross-referencing data points. No more having to check if a ship's name matches its IMO number across three different sheets; the system handles the ID resolution automatically. You also eliminate waiting for separate API keys or credentials on multiple platforms.

It’s about context, period. Instead of just getting raw JSON data dumps from six different endpoints, you get an answer that puts all the pieces—the location, the history, and the specs—into a single narrative.

Common Questions About VesselAPI MCP

How do I find out what kind of vessel it is using VesselAPI? +

You use get_vessel_details for this. Just provide the IMO number, and the tool returns comprehensive information including the ship's type (e.g., Container Ship) and its flag.

Can I track a vessel if I only know its name? Which tool should I use? +

Start with search_vessels. This tool takes the name you have and searches the database to find matching vessels, which will give you the necessary IDs for further checks.

How do I know if my connection to VesselAPI is working? +

You run the check_api_status tool. This simply confirms that the server is operational and ready for your agent to start pulling data.

Does VesselAPI track historical positions, or just real-time ones? +

While get_vessel_position gets the latest AIS data, you can audit its past movement using get_vessel_schedules, which tracks planned and historical port calls.

How do I manage my data consumption when using the `check_api_status` tool? +

The status check provides immediate metadata regarding your current usage limits. You monitor this endpoint to track your research volume and ensure you stay within established API call rates.

What is required before my AI agent can run the `get_vessel_details` tool? +

You must first subscribe to the VesselAPI server and provide your unique API key. This key authorizes all calls, allowing your agent to access comprehensive global vessel data.

Can I use the `list_maritime_ports` tool to get metadata for multiple locations? +

Yes, you first run list_maritime_ports to retrieve a list of supported global ports. You then pass specific port IDs or names from that output to refine your local data planning.

What should I do if the `search_vessels` tool returns too many results? +

The API handles large result sets using pagination, returning a limited page of matches. You must pass parameters like search page number or sorting criteria to narrow down your scope.

How do I find my VesselAPI Key? +

Log in to your VesselAPI dashboard, and you will find your API Key under the settings page. Copy and paste it below.

Does it support real-time AIS data? +

Yes. The get_vessel_position tool provides the latest AIS position received for the specified vessel IMO number.

Can the agent show port schedules? +

Yes. Use the get_vessel_schedules tool to retrieve upcoming port calls and arrival/departure metadata for any vessel.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 6 tools

We've already built the connector for VesselAPI. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.