Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"marinetraffic": {
"env": {
"MARINETRAFFIC_API_KEY": "your-api-key-here"
},
"args": [
"/path/to/marinetraffic-server/build/index.js"
],
"command": "node",
"disabled": false,
"autoApprove": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server that provides access to MarineTraffic vessel tracking data.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@Cyreslab-AI/marinetraffic-mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @Cyreslab-AI/marinetraffic-mcp-server against OSV.dev.
Click any tool to inspect its schema.
vesselInformation about a vessel by MMSI or IMO number
vessel://{identifier}
vessels_in_areaList of vessels in a specified geographic area
vessels://area/{lat}/{lon}/{radius}
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in maps
A Model Context Protocol (MCP) server providing TomTom's location services, search, routing, and traffic data to AI agents.
Real-time BART departures, trip planning, fares, stations, and advisories.
MCP server for the VesselAPI — maritime vessel tracking, port events, emissions, and navigation data
Fair meeting point discovery for AI agents with isochrone-based travel time fairness
MCP Security Weekly
Get CVE alerts and security updates for Marinetraffic Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that provides access to MarineTraffic vessel tracking data.
This MCP server provides the following capabilities:
To install MarineTraffic Vessel Tracking Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @Cyreslab-AI/marinetraffic-mcp-server --client claude
cd marinetraffic-server
npm install
npm run build
The server requires a MarineTraffic API key to function. You can provide this through the environment variable MARINETRAFFIC_API_KEY.
To use this server with Claude, add it to your MCP settings configuration file:
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"marinetraffic": {
"command": "node",
"args": ["/path/to/marinetraffic-server/build/index.js"],
"env": {
"MARINETRAFFIC_API_KEY": "your-api-key-here"
},
"disabled": false,
"autoApprove": []
}
}
}
Edit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json:
{
"mcpServers": {
"marinetraffic": {
"command": "node",
"args": ["/path/to/marinetraffic-server/build/index.js"],
"env": {
"MARINETRAFFIC_API_KEY": "your-api-key-here"
},
"disabled": false,
"autoApprove": []
}
}
}
Once the server is configured and running, you can use it with Claude to access vessel tracking data:
<use_mcp_tool>
<server_name>marinetraffic</server_name>
<tool_name>get_vessel_position</tool_name>
<arguments>
{
"identifier": "123456789"
}
</arguments>
</use_mcp_tool>
<use_mcp_tool>
<server_name>marinetraffic</server_name>
<tool_name>search_vessels</tool_name>
<arguments>
{
"vessel_name": "MAERSK"
}
</arguments>
</use_mcp_tool>
<use_mcp_tool>
<server_name>marinetraffic</server_name>
<tool_name>get_vessels_in_area</tool_name>
<arguments>
{
"latitude": 37.8199,
"longitude": -122.4783,
"radius": 10
}
</arguments>
</use_mcp_tool>
<access_mcp_resource>
<server_name>marinetraffic</server_name>
<uri>vessel://123456789</uri>
</access_mcp_resource>
The MarineTraffic API has usage limits based on your subscription plan. Be aware of these limits when using the server to avoid exceeding your quota.