MCP server for the VesselAPI — maritime vessel tracking, port events, emissions, and navigation data
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"vesselapi": {
"env": {
"VESSELAPI_API_KEY": "your-api-key"
},
"args": [
"-y",
"vesselapi-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP (Model Context Protocol) server that exposes maritime data from the VesselAPI to AI assistants like Claude Desktop, Cursor, Windsurf, and Claude Code.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 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 npm against OSV.dev.
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 analytics
An MCP server that provides [describe what your server does]
MCP server that enables AI agents to perform comprehensive web audits using Google Lighthouse with 13+ tools for performance, accessibility, SEO, and security analysis.
MCP server for Dynatrace Managed to access logs, events, and metrics.
Access Dynatrace observability data: logs, metrics, problems, vulnerabilities via DQL and Davis AI
MCP Security Weekly
Get CVE alerts and security updates for io.github.vessel-api/vesselapi-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP (Model Context Protocol) server that exposes maritime data from the VesselAPI to AI assistants like Claude Desktop, Cursor, Windsurf, and Claude Code.
VESSELAPI_API_KEY in the configuration belowResources: Documentation | API Explorer | Dashboard | Contact Support
A hosted deployment is available on Fronteir AI.
No installation required — just configure your AI client with npx:
{
"mcpServers": {
"vesselapi": {
"command": "npx",
"args": ["-y", "vesselapi-mcp"],
"env": {
"VESSELAPI_API_KEY": "your-api-key"
}
}
}
}
Add the JSON above to the config file for your client:
| Client | Config file |
|---|---|
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) |
| Cursor | .cursor/mcp.json or ~/.cursor/mcp.json |
| Claude Code | .claude/settings.json or ~/.claude/settings.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Tool | Description |
|---|---|
search_vessels | Search vessels by name, IMO, MMSI, flag, type, callsign, year built, class society, or owner |
get_vessel | Get detailed vessel information |
get_vessel_position | Get current vessel position (lat/lon, speed, heading) |
get_vessel_eta | Get vessel estimated time of arrival |
get_vessel_classification | Get classification details (class society, surveys, hull) |
get_vessel_ownership | Get ownership details (owner, manager, operator) |
get_vessel_emissions | Get emissions data (CO2, fuel consumption) |
get_vessel_inspections | Get port state control inspections |
get_vessel_casualties | Get marine casualty records |
get_vessel_inspection_detail | Get detailed information about a specific inspection |
get_vessel_positions_batch | Get positions for multiple vessels at once (with optional time range) |
| Tool | Description |
|---|---|
search_ports | Search ports by name, country, type, size, region, harbor size, or harbor use |
get_port | Get port details by UN/LOCODE |
get_port_events | Get arrivals/departures for a port |
get_port_events_by_vessel | Get port events for a vessel |
list_port_events | List port events globally with filters for time, country, port, vessel, or event type |
search_port_events_by_port | Search port eve |