Vessel Traffic MCP vs Geowire

In-depth architectural comparison of the Vessel Traffic MCP and Geowire MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Vessel Traffic MCP when:

• You need dedicated capabilities in the Location Services domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Read-only vessel identity lookup, AIS-style positions, areas, and tracks, Port call and shipping schedule searches.

Explore Vessel Traffic MCP Details

Choose Geowire when:

• You need dedicated capabilities in the Location Services domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: search_places, get_place, geocode_address.

Explore Geowire Details

Feature & Specification Comparison

Specification	Vessel Traffic MCP tools-mcp Location Services	Geowire geowire Location Services
Summary	Read-only vessel identity lookup, AIS-style positions, tracks, port calls, carrier schedules, vessel schedules, and delay heuristics with source attribution and BYOK provider support.	Location intelligence gateway across 10 providers (OpenStreetMap, OSRM, Google, Yelp, Foursquare, US Census, Kakao, Naver, Baidu, your own CSV): place search, geocoding, directions + distance matrices, travel-time isochrones, and commercial-area analysis (category density, ratings, demographics). Multi-provider merge + dedup with per-field provenance, cost budgets, and a policy engine that enforces each provider’s caching/attribution terms. Works with zero API keys. npx -y @geowirehq/mcp

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "tools-mcp-vessel-traffic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tools-mcp/vessel-traffic-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "geowire-geowire": {
      "command": "npx",
      "args": [
        "-y",
        "@geowirehq/cli"
      ]
    }
  }
}

Related MCP Server Comparisons