MCP server for the VesselAPI — maritime vessel tracking, port events, emissions, and navigation data
MCPpedia last refreshed this data
io.github.vessel-api/vesselapi-mcp is an MCP server that MCP server for the VesselAPI — maritime vessel tracking, port events, emissions, and navigation data. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 56/100 on MCPpedia's security, maintenance and efficiency rubric.
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.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
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
MCP Server for GCP environment for interacting with various Observability APIs.
Deterministic, persistent graph server for tracking workflow state, decisions, and blockers.
MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.
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 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. 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 mcp add, which writes .mcp.json in the project or ~/.claude.json for user scope |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Tool | Description |
|---|---|
search_vessels | Search vessels by name, IMO, MMSI, flag, type, callsign, or year built |
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_emissions | Get emissions data (CO2, fuel consumption) |
get_vessel_casualties | Get marine casualty records |
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_inbound | Get vessels inbound to a port within an ETA window |
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 events by port name |
search_port_events_by_vessel | Search port events by vessel name |
get_vessel_last_port_event | Get the most recent port event for a vessel |
| Tool | Description |
|---|---|
list_emissions | List global vessel emissions data with optional year filter |
|