Help wanted: share Vessel Traffic MCP with maritime/logistics users

[seokmogu]

We need help getting Vessel Traffic MCP in front of people who can actually use or evaluate maritime/logistics workflows.

This is not a request to spam links. The useful help is small, specific, and source-attributed.

Useful ways to help

• Share the repository with one MCP, logistics, forwarding, shipping, trade, SCM, or maritime-software community.
• Install it with an MCP client and report whether the setup worked.
• Try one vessel-position prompt and one carrier-schedule prompt.
• Tell us which real workflow matters: ETA checks, vessel/port-call monitoring, carrier schedule comparison, exception alerts, or B/L-to-vessel lookup.
• Request a provider adapter for a data source you already use and can legally access.
• Improve client-specific install docs after testing Claude Desktop, Claude Code, Codex, Cursor, VS Code, or another MCP client.

Copy/paste sharing kit

https://github.com/tools-mcp/vessel-traffic-mcp/blob/main/docs/marketing/help-us-spread.md

Canonical links

• GitHub: https://github.com/tools-mcp/vessel-traffic-mcp
• npm: https://www.npmjs.com/package/@tools-mcp/vessel-traffic-mcp
• MCP Registry: io.github.tools-mcp/vessel-traffic-mcp

Boundaries

• Do not claim this is a navigation product.
• Do not claim provider data ownership.
• Do not imply paywall, CAPTCHA, login, or provider-term bypass.
• Do mention read-only tools, source URLs, and BYOK for commercial providers.