Open Waters AIS vs Vessel Traffic MCP
A side-by-side look at the Open Waters AIS and Vessel Traffic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Open Waters AIS for location services work over a hosted endpoint; choose Vessel Traffic MCP for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Open Waters AIS when
- You need dedicated capabilities in the Location Services domain.
- You prefer a remote HTTP/SSE transport.
Choose Vessel Traffic MCP when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 43/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 6 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Open Waters AIS | View Vessel Traffic MCP |
Tools & capabilities
Open Waters AIS tools
No tool names declared yet. Check the project README from the listing page.
Vessel Traffic MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Open Waters AIS
{
"mcpServers": {
"open-waters-ais": {
"url": "https://ais.openwaters.io/mcp"
}
}
}
Vessel Traffic MCP
{
"mcpServers": {
"tools-mcp-vessel-traffic-mcp": {
"command": "npx",
"args": [
"-y",
"@tools-mcp/vessel-traffic-mcp"
]
}
}
}
Frequently asked questions
Open Waters AIS is categorized under Location Services and uses a remote HTTP/SSE transport. Vessel Traffic MCP belongs to Location Services and uses a local stdio subprocess. Pick Open Waters AIS for location services work and Vessel Traffic MCP for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Open Waters AIS has no declared pricing — check the project's own site. Vessel Traffic MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add open-waters-ais and tools-mcp-vessel-traffic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Open Waters AIS has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 7 GitHub stars. Vessel Traffic MCP has 56/100 (Good) with 3 views, 0 installs and 6 GitHub stars.