MCP Tools DirectoryAbout this integration
Read-only MCP server for vessel AIS, ship tracking, schedules, and BYOK maritime providers.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.0
- Package
- @tools-mcp/vessel-traffic-mcp
- Last compatibility test
- Not independently tested
Connect your agent
@tools-mcp/vessel-traffic-mcpPublisher documentation and executable manifest reviewed. Authentication varies by provider and transport; package and provider endpoints were not executed or independently security-audited.
Capabilities: Search and resolve vessel identities, Read configured vessel positions, tracks, and port calls, Search configured carrier and vessel schedules, Report provider provenance and onboarding requirements
Connected profiles
Additional details
io.github.tools-mcp/vessel-traffic-mcp
Source ↗ · Checked 2026-09-170.1.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17@tools-mcp/vessel-traffic-mcp
Source ↗ · Checked 2026-09-200.1.0
Source ↗ · Checked 2026-09-20An MCP client can launch the npm package as a local stdio process; publisher documentation also describes a separately configured Streamable HTTP mode.
Source ↗ · Checked 2026-09-20The documented access model is mixed: fixture mode needs no account or API key, public adapters are opt-in, commercial/community providers use user-owned credentials, and remote HTTP can use a bearer token. The native authentication taxonomy cannot represent all of these modes, so authentication is classified as unknown.
Source ↗ · Checked 2026-09-20For the reviewed catalog connection, a local MCP client starts npx with -y and @tools-mcp/vessel-traffic-mcp over stdio; the existing endpoint remains null.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20