JSONCargo Maritime MCP for AI. Audit global vessel movements and port data instantly.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
JSONCargo Maritime lets your AI agent handle all global shipping data requests. Search vessels by name or IMO number, audit current voyage status, and retrieve detailed port metadata without needing to log into any separate maritime portal.
It turns complex, multi-site logistics research into a single conversation with your agent.
What your AI can do
Check api status
Verifies if the JSONCargo data service is currently operational and accessible.
Get current voyage details
Retrieves all tracking metadata for a vessel that is actively sailing on its route.
List maritime ports
Provides a searchable list of every global port registered in the database, along with their location codes.
Find records on thousands of ships using either their name or official IMO number.
Retrieve the full metadata and status for a ship currently in transit.
Access an official catalog of ports, including their unique location codes (LOCODEs).
Confirm that the underlying JSONCargo data source is operational and running.
Ask an AI about this
Waiting for input…
JSONCargo Maritime: 4 Tools for Logistics Data
Use these four tools to search ships by name or IMO number, list global ports, audit current voyage details, and confirm the data source status.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using JSONCargo Maritime on VinkiusCheck Api Status
Verifies if the JSONCargo data service is currently operational and accessible.
Get Current Voyage Details
Retrieves all tracking metadata for a vessel that is actively sailing on its route.
List Maritime Ports
Provides a searchable list of every global port registered in the database, along...
Search Maritime Vessels
Locates specific vessels by searching using either their official IMO number or...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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
Make Your AI Do More
Start with JSONCargo Maritime, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by JSONCargo. 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
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 connection provides 4 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The pain of manual shipping research is massive.
Today, if you need a full picture of trade activity, your process looks like this: You jump to one port authority site for LOCODEs. Then you switch to a tracking platform to find vessel statuses. Next, you use a separate registry to confirm the ship's ownership metadata. It’s a cycle of tabs, logins, and copy-pasting.
With this MCP, your agent handles all that friction. You ask one question—for example, 'What are the current details for ships passing through Rotterdam?' Your agent pulls the port data, checks the vessel status, and compiles it into one clean answer. The time sink disappears.
Accessing real-time data via JSONCargo Maritime.
You no longer have to run separate queries for each piece of information. You can ask your agent to list the ports first, and then immediately use those LOCODEs in a request to find vessels that passed through them. It's all orchestrated in one go.
What changes now is control. You get immediate access to reliable, structured data from an industry-leading source without needing deep API knowledge or spending hours on manual cross-referencing.
What your AI can actually do with this
Tracking ships and auditing trade routes used to be a manual nightmare. You'd have to jump between multiple global shipping portals, running different searches just to piece together a vessel’s history or current location. Now, you connect JSONCargo Maritime to your agent, and it handles the whole workflow. Your AI client acts like a dedicated maritime consultant, retrieving real-time data on thousands of ships and ports instantly.
You can ask your agent to audit a voyage's status or pull up detailed metadata for any port worldwide. This capability is hosted right here on Vinkius, meaning you connect once from any MCP-compatible client and get access to this entire maritime dataset. Whether you’re running supply chain research or just monitoring regional trade constraints, the data stays verified and precise.
019d844c-c12a-7030-af54-9f3134df607a Here's how it actually works
The bottom line is, once configured, your agent uses this MCP as a single source for all global shipping data.
Subscribe to this MCP and provide your unique JSONCargo API key.
Connect your preferred AI client (like Claude or Cursor) to Vinkius using the credentials.
Tell your agent what you need—for instance, 'What is the status of vessel X?'—and it runs the necessary queries.
Who is this actually for?
This connector is built for people who spend time tracking physical assets and complex international supply chains. If you’re tired of copying dates, port codes, and vessel names from five different websites just to write a single report, this MCP saves your day.
Uses the tool to monitor specific vessels' timelines and pull arrival metadata directly into their analysis reports.
Verifies port locations and audits potential shipping routes using the global catalog before finalizing a plan.
Performs rapid, deep-dive audits of vessel metadata to identify key markers in regional trade patterns.
What Changes When You Connect
Avoid manual lookups: Instead of searching multiple sites for a ship's details, you simply ask your agent to use search_maritime_vessels by name or IMO number. It gets the metadata directly.
Know where ships are right now: Use get_current_voyage_details to pull real-time status and position data for any vessel without needing a dedicated tracking dashboard.
Control your routes with certainty: The list_maritime_ports tool gives you access to the full catalog of global ports, letting you verify LOCODEs before planning anything.
Build reliable workflows: Running check_api_status first confirms that all the data sources are online and ready for deep-dive research. No guesswork involved.
Faster reporting: You can combine tools like searching vessels and listing ports to build complex reports in one conversational turn, saving hours of copy/pasting.
See it in action
A shipment is delayed; I need its current location.
I'm worried about the cargo. My agent needs to know where it is right now. I ask it, 'What's the status of vessel ID ABC-123?' The agent uses get_current_voyage_details and gives me the exact route and last updated position.
I need to check if a port is valid for my new route.
The planner needs to build a new trade corridor. I ask the agent to list all ports in Singapore. It runs list_maritime_ports and returns the full, verifiable LOCODE catalog for me to use.
A competitor's ship pops up in my research.
I need quick data on a vessel I just heard about. I ask the agent to find it by its name. It uses search_maritime_vessels and gives me the full metadata, including its flag type.
We are running a major audit of our whole network.
I need to confirm that all my data feeds work before I run reports. I ask the agent to check the service health. It runs check_api_status and confirms everything is green, so I know the report will be accurate.
The honest tradeoffs
Assuming data availability
Just running a search query without checking if the source API key or connection status is valid.
Always start by confirming service health. Run check_api_status first. This confirms that all other calls, like using search_maritime_vessels, will actually return data.
Using vague search terms
Asking the agent to 'find ships near the Caribbean' without specifying a known port or vessel ID.
Be specific. First, use list_maritime_ports to get the exact LOCODEs for the region, then feed those codes back into your request.
Missing voyage details
Only getting a ship's static metadata without knowing where it is right now.
Don't just search. For active ships, always follow up with get_current_voyage_details to understand its real-time position and status.
When It Fits, When It Doesn't
Use this MCP if your work revolves around auditing physical movement, verifying international logistics routes, or cross-referencing large datasets of maritime assets. If you need to know where a ship is right now or what ports exist globally, this is the tool. Don't use it if you are simply trying to search for general company contact information, or if your data needs relate only to internal employee records—those require different types of connectors. This MCP excels at raw, verifiable global positioning and asset status.
Questions you might have
How do I check if the JSONCargo Maritime MCP connection is working? +
Run the check_api_status tool. This immediately confirms if the data source is operational, which you should always run as your first step in any audit workflow.
What information can I get using search_maritime_vessels? +
This tool finds ships by name or IMO number and retrieves key metadata like the vessel type and flag. It's perfect for initial identification before tracking its movement.
Can list_maritime_ports help me with a route plan? +
Yes, it gives you the full global catalog of ports and their specific LOCODEs. You use these codes to verify that your planned route touches established, verifiable terminals.
Does get_current_voyage_details give me historical data? +
No, this tool focuses on the vessel's current status and position—the active voyage details. If you need historical logs, your agent can combine this with other sources.
How do I handle rate limits when calling `get_current_voyage_details`? +
The MCP will return a specific HTTP status code indicating throttling. Your agent must implement exponential backoff logic; wait longer after each failed attempt to prevent service interruption.
Does `search_maritime_vessels` require the full IMO number, or can I use partial names? +
You do not need a perfect match. While exact IMO numbers yield the best results, you can search using vessel names or partial identifiers; the system cross-references available metadata.
Can `list_maritime_ports` filter results by specific countries or regions? +
Yes, the tool accepts regional parameters. You must pass a country code (e.g., 'US' for United States) in the input to narrow down the global port list effectively.
What should I consider when running multiple searches using `search_maritime_vessels`? +
The system is built for high volume, but sustained, rapid querying can hit rate limits. It's best practice to space out bulk requests or utilize batch processing within your agent workflow.
How do I find my JSONCargo API Key? +
Log in to your JSONCargo account, navigate to your dashboard, and you will find your API Key in the 'Access Tokens' section. Copy and paste it below.
What vessel identifiers are supported? +
The API supports searching by vessel name, IMO number, and unique JSONCargo identifiers.
Does it support real-time positions? +
Yes. The get_current_voyage_details tool retrieves the most recent position and status metadata for active vessels.
We've already built the connector for JSONCargo Maritime. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 4 tools are live and waiting.
You're up and running in seconds.
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.
Built, hosted, and secured by Vinkius. You just connect and go.