Vessel Traffic MCP vs io.github.vessel-api/vesselapi-mcp
Vessel Traffic MCP is an MCP server published by tools-mcp. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.vessel-api/vesselapi-mcp is an MCP server published by vessel-api. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Vessel Traffic MCP |  io.github.vessel-api/vesselapi-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (npm): 136 Downloads/week (npm): 35 Forks (GitHub): 1 Stars (GitHub): 8 Not marked · First seen |
Listed Version: 2.2.0 Downloads/month (npm): 640 Downloads/week (npm): 79 Forks (GitHub): 2 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Vessel Traffic MCP | io.github.vessel-api/vesselapi-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 8 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 1 (worse) | 2 (better) |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | On your machine (@tools-mcp/vessel-traffic-mcp) | On your machine (vesselapi-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/tools-mcp/vessel-traffic-mcp | github.com/vessel-api/vesselapi-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Vessel Traffic MCP
Read-only MCP server for vessel AIS, ship tracking, schedules, and BYOK maritime providers.
io.github.vessel-api/vesselapi-mcp
MCP server for the VesselAPI: maritime vessel tracking, port events and emissions
How to run each
Vessel Traffic MCP As a local MCP server: npm package
claude mcp add --transport stdio vessel-traffic-mcp -- npx -y @tools-mcp/vessel-traffic-mcpio.github.vessel-api/vesselapi-mcp As a local MCP server: npm package
claude mcp add --transport stdio vesselapi-mcp -- npx -y vesselapi-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.vessel-api/vesselapi-mcp publish no settings it asks for, so we do not compare settings.
What it can do: Vessel Traffic MCP · What it can do: io.github.vessel-api/vesselapi-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.