JSONCargo Maritime MCP. Audit global vessels and port activity instantly.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
JSONCargo Maritime. Track global vessels and audit port data via AI. This server lets your agent query real-time shipping data, search vessels by name or IMO, and list global ports.
It transforms complex maritime research into simple conversation, giving you instant access to voyage status and metadata without hitting a single portal.
It's the central hub for logistics intelligence.
What your AI agents can do
Check api status
Verifies if the JSONCargo service is currently operational.
Get current voyage details
Retrieves the full metadata for a vessel's current voyage using a specific vessel ID.
List maritime ports
Lists all global ports registered in the JSONCargo database.
Searches the database for maritime vessels using either a name or an IMO number.
Retrieves the full metadata and current operational status for a specific vessel's voyage.
Pulls a catalog of all globally registered maritime ports and their associated location codes.
Checks the live operational status of the JSONCargo service API.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
JSONCargo Maritime MCP Server: 4 Tools for Maritime Data
These four tools allow your AI agent to verify API status, search vessels by name or IMO, list global ports, and retrieve current voyage details.
019d844ccheck api status
Verifies if the JSONCargo service is currently operational.
019d844cget current voyage details
Retrieves the full metadata for a vessel's current voyage using a specific vessel ID.
019d844clist maritime ports
Lists all global ports registered in the JSONCargo database.
019d844csearch maritime vessels
Searches for maritime vessels using either a name or an 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
Make Your AI Do More
Start with JSONCargo Maritime, 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
You're tracking global supply chains, right? This server gives your agent direct access to real-time maritime data, letting it skip the usual mess of multiple shipping portals. It handles all the heavy lifting—searching vessels, checking voyage status, and pulling port details—all from one spot. You just talk to your agent, and it gets the facts.
search_maritime_vessels lets your agent look up any maritime vessel using either a name or an IMO number. You get the vessel's detailed metadata when you run it.
Need to know where a ship is? get_current_voyage_details pulls the full metadata and current operational status for a specific vessel's voyage when you give it a vessel ID. You get the whole picture of the voyage.
Want to map out trade routes? list_maritime_ports lists every global port registered in the JSONCargo database, giving you their location codes.
Before you start, you gotta make sure the connection's good. check_api_status verifies if the JSONCargo service is currently operational, so you know your research workflow won't get stuck.
Your agent handles all this stuff. You don't have to remember what tool does what. Just ask your agent about a vessel by name or IMO number, and it'll run search_maritime_vessels. Need to know that vessel's current journey? Tell your agent to use get_current_voyage_details with the ID. If you need to pull a list of all the ports on the map, list_maritime_ports gives you the catalog.
You'll always know if it's working because check_api_status verifies the live API status.
How JSONCargo Maritime MCP Works
- 1 First, your agent runs
check_api_statusto confirm the service is operational. This prevents wasting time on failed calls. - 2 Next, if you need to locate a port, you call
list_maritime_portsto get the global LOCODE catalog. If you know the vessel ID, you useget_current_voyage_detailsto get the real-time location. - 3 Finally, you use
search_maritime_vesselsto confirm the vessel's identity before querying its current status. The agent compiles all this data into a single, actionable report.
The bottom line is, your AI client treats the entire maritime data stack as one continuous data source, allowing you to ask complex, multi-step questions without manual data stitching.
Who Is JSONCargo Maritime MCP For?
Anyone who spends time cross-referencing shipping manifests or manually querying multiple logistics websites needs this. It's for the supply chain analyst who needs to monitor vessel movements and the trade researcher who needs instant, verifiable data on global port activity. If your job involves tracking where something is, this saves hours of clicking.
Uses the agent to monitor vessel timelines and pull arrival metadata directly into their analysis workflow.
Verifies port locations and audits complex shipping patterns, ensuring routes comply with current operational data.
Performs rapid audits of vessel metadata and identifies relevant logistics markers using natural language prompts.
Automates maritime data querying to coordinate cross-functional shipping teams and decision-making.
What Changes When You Connect
- See the current location and metadata of a vessel by calling
get_current_voyage_detailswith a vessel ID. This gives you real-time status, eliminating the need to cross-reference separate tracking websites. - Build comprehensive logistics maps by running
list_maritime_ports. You get the full LOCODE and terminal data for every global port, which is critical for planning trade routes. - Instantly identify vessels using
search_maritime_vessels. You only need a name or IMO number to pull up key metadata like flag or vessel type, bypassing manual lookups. - Validate your entire workflow by running
check_api_status. Knowing the service is live means your agent won't fail halfway through a critical query. - Run multi-step audits. You can first
search_maritime_vesselsto confirm an asset, then use that ID inget_current_voyage_detailsfor the most precise data. - Keep data precise. All data pulled is verified against the JSONCargo database, so you don't have to worry about manual data entry or source discrepancies.
Real-World Use Cases
Tracking a Missing Shipment
A supply chain analyst needs to know where the cargo is. They prompt their agent: 'What is the current voyage status for the vessel with IMO 9811000?' The agent immediately uses get_current_voyage_details to provide the current location and voyage path, solving the problem instantly.
Planning a New Trade Route
A logistics planner is mapping a route through Southeast Asia. They use list_maritime_ports to pull the full catalog of ports, then use that list to narrow down search areas before asking the agent to check the expected entry points.
Due Diligence on a New Partner
A trade researcher must verify a potential partner's fleet. They run search_maritime_vessels with the partner's fleet name. The agent retrieves the vessel metadata, allowing the researcher to quickly assess the type and flag of the assets without leaving their chat window.
Debugging a Logistics Workflow
An operations lead needs to know if the entire tracking system is online. They first run check_api_status. If the status is good, they proceed to use search_maritime_vessels to test the data flow, ensuring the system is fully functional before deployment.
The Tradeoffs
Searching by general location
Asking the agent, 'Show me all the ports near the Mediterranean Sea.' This is too vague and the tools require specific LOCODEs or ports to function.
→
First, run list_maritime_ports to get a list of candidate ports in that region. Then, you can use search_maritime_vessels or get_current_voyage_details if you have a specific vessel ID or known port name.
Assuming real-time data is available
Just asking, 'Where is the Ever Given right now?' without providing a vessel ID or IMO. The system can't guess the asset.
→
Always start by confirming the vessel's identity. Use search_maritime_vessels with the vessel's name or IMO number. Once you have the vessel ID, then call get_current_voyage_details for the real-time status.
Skipping the connection check
Relying on a complex query like 'What is the status of the fleet?' without verifying the server connection first. This leads to confusing, non-specific errors.
→
Per the API spec, always check the status of check_api_status first. If the status returns 'Operational,' then proceed with any other data retrieval tool.
When It Fits, When It Doesn't
Use this server if your core need is maritime intelligence: tracking vessels, cataloging ports, or auditing supply chain movements. You need the data to be structured and verifiable, like real-time status or LOCODEs. Don't use this if you just need general market analysis or historical trends over decades; the tools focus on current status and location. If your problem is simply 'I need to talk to a human,' this won't help—it's a data source, not a communications platform. If you need to validate the structural integrity of the data, use check_api_status first. If you only know a vessel's name, use search_maritime_vessels. If you know the vessel ID, use get_current_voyage_details—it's far more specific and reliable for status checks.
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 server provides 4 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manual maritime research involves jumping between port authority sites and vessel databases.
Today, tracking a vessel means logging into one portal for the vessel's manifest, another for its port of origin, and a third for its current location. You copy IDs, cross-reference LOCODEs, and wait for pages to load. It’s slow, and the data is never in one place.
With JSONCargo Maritime, your agent handles the whole sequence. You ask a single question—like, 'What's the status of the cargo near Rotterdam?'—and the agent uses `list_maritime_ports` and `search_maritime_vessels` to pull all necessary details. You get the answer, verified and consolidated, in one chat.
JSONCargo Maritime MCP Server: Get real-time vessel data.
Forget the steps of searching by name, then finding the ID, and finally running a separate status query. The agent handles the dependency chain. It figures out that to get the voyage details, it needs the vessel ID, and it finds that ID using `search_maritime_vessels` automatically.
This isn't just querying data; it's building a reliable data pipeline on demand. Your AI client now acts as the maritime expert, making complex, multi-step queries as easy as asking a question.
Common Questions About JSONCargo Maritime MCP
How do I check a vessel's real-time location using JSONCargo Maritime? +
You must first identify the vessel using search_maritime_vessels to get its unique ID. Then, use get_current_voyage_details with that ID to get the most accurate, real-time status and metadata.
Is `list_maritime_ports` faster than searching for a single port? +
Listing ports gives you the entire catalog of global LOCODEs, which is useful for scope checking. Searching for a vessel is the faster way to get status, but listing ports is necessary for understanding the trade landscape.
What if I only know the vessel's name, not the IMO number? +
Use search_maritime_vessels. This tool accepts either the vessel's name or the IMO number, so you don't need both pieces of information to start the search.
How do I make sure the server is working before I start my analysis? +
Always start by calling check_api_status. This simple call confirms the API is operational, ensuring all subsequent data calls won't fail due to a service outage.
What information can I get when I use `search_maritime_vessels`? +
The search_maritime_vessels tool returns detailed vessel metadata, including flags and types. You'll get identifiers, names, and core specifications to classify the ship.
How do I check the current status of a ship's journey using `get_current_voyage_details`? +
It pulls the full metadata for the vessel's active journey. This includes the 'En Route' status, origin, destination, and the time the position was last updated.
Does `list_maritime_ports` provide location codes for every port? +
Yes, the list_maritime_ports tool provides global ports and their associated LOCODEs. This ensures precise, standardized data for every trade route you track.
What should I do if I run into an error when calling `check_api_status`? +
If check_api_status fails, the JSONCargo service is down or unreachable. Check your API key and ensure your network connection is stable before retrying the request.
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
ANEEL Dados Abertos
Access the Brazilian National Electric Energy Agency (ANEEL) Open Data Portal to query electricity sector datasets, resources, and records.
Mapbox
Geocode addresses, get directions, calculate distances and generate maps with Mapbox's location platform.
CVM Dados Abertos
Access Brazilian capital markets data directly from the CVM Open Data portal — query investment funds, listed companies, and financial reports.
You might also like
Aspire
Manage influencer marketing campaigns and creators with Aspire — track projects, members, and content via AI.
BlockPi (Distributed RPC Network)
Access distributed blockchain RPC nodes via BlockPi — monitor RU balances, track consumption, and execute JSON-RPC calls across multiple networks.
Customerly
Combine live chat, email marketing, and customer surveys in one platform that helps SaaS companies grow and retain users.