vessel-traffic-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VESSEL_MCP_HTTP_HOST | No | HTTP host for http transport | 127.0.0.1 |
| VESSEL_MCP_HTTP_PORT | No | HTTP port for http transport | 8765 |
| VESSEL_MCP_TRANSPORT | No | Transport mode (stdio or http) | stdio |
| VESSEL_MCP_AUTH_TOKEN | No | Bearer token for HTTP authorization | |
| VESSEL_MCP_ENABLE_BYOK_PROVIDERS | No | Comma-separated list of BYOK providers to enable | |
| VESSEL_MCP_ENABLE_PUBLIC_PROVIDERS | No | Comma-separated list of public providers to enable (e.g., myshiptracking,tradlinx) | |
| VESSEL_MCP_PROFILE_AISHUB__API_KEY | No | API key for AISHub BYOK provider | |
| VESSEL_MCP_PROFILE_AISSTREAM__API_KEY | No | API key for AISStream BYOK provider | |
| VESSEL_MCP_PROFILE_VESSELAPI__API_KEY | No | API key for VesselAPI BYOK provider | |
| VESSEL_MCP_PROFILE_DATADOCKED__API_KEY | No | API key for Data Docked BYOK provider | |
| VESSEL_MCP_PROFILE_DATALASTIC__API_KEY | No | API key for Datalastic BYOK provider | |
| VESSEL_MCP_PROFILE_BARENTSWATCH__API_KEY | No | API key for BarentsWatch BYOK provider | |
| VESSEL_MCP_PROFILE_VESSELFINDER__API_KEY | No | API key for VesselFinder BYOK provider | |
| VESSEL_MCP_PROFILE_MARINETRAFFIC__API_KEY | No | API key for MarineTraffic BYOK provider | |
| VESSEL_MCP_PROFILE_GLOBALFISHINGWATCH__API_KEY | No | API key for Global Fishing Watch BYOK provider | |
| VESSEL_MCP_PROFILE_SEARATES_SCHEDULES__API_KEY | No | API key for SeaRates Schedules BYOK provider | |
| VESSEL_MCP_PROFILE_ROUTESCANNER_CONNECT__API_KEY | No | API key for Routescanner Connect BYOK provider |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| provider_statusA | List configured vessel data providers, auth state, feature support, quota hints, and caveats. |
| data_sourcesA | List available vessel data source adapters, coverage notes, auth mode, and caveats. |
| credential_profilesA | List BYOK credential profile labels, provider hints, declared field names, and status. Raw keys are never returned. |
| provider_onboardingA | Show safe manual signup, API docs, credential env vars, configured status, and validation steps for provider access. Does not create accounts or issue credentials. |
| vessel_searchA | Search vessels by MMSI, IMO, name, or callsign. Requires at least one identifier; returns normalized identities with provider source metadata. |
| vessel_name_resolveA | Resolve a messy vessel name (e.g. from B/L text) to ranked MMSI/IMO candidates with matched/missing signals and confidence. |
| document_vessel_lookupB | Extract vessel signals (name, IMO/MMSI/callsign, voyage, ports, container numbers, dates) from B/L-style text and return ranked candidates. |
| vessel_positionA | Return the latest known position for a vessel by MMSI or IMO with source, retrievedAt, observedAt, and freshness metadata. |
| vessel_areaA | Return latest known positions for vessels inside a bounding box (latMin<=latMax, lonMin<=lonMax) with provider source metadata. |
| vessel_trackB | Return the recent track points for a vessel by MMSI or IMO, optionally bounded by ISO-8601 windowStart/windowEnd. |
| port_callsB | Return recent port-call events for a vessel by MMSI/IMO or for a UN/LOCODE port. Requires at least one filter. |
| carrier_schedule_searchB | Search carrier sailing schedules by origin/destination, carrier SCAC/name, cargo type, direct-only flag, and departure/arrival windows. Returns normalized schedules with upstream source metadata. |
| vessel_scheduleB | Return scheduled carrier port calls for a vessel by MMSI, IMO, vessel name, voyage number, or carrier SCAC with source metadata. |
| schedule_delay_predictA | Compare planned carrier schedule timestamps with estimated/actual timestamps and return an on-time, at-risk, delayed, or unknown heuristic. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tools-mcp/vessel-traffic-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server