Skip to main content
Glama
Sign In

Container Tracking MCP

by io.github.lxxmng
OverviewDiscussionsAdmin

Server Details

DCSA container tracking across 228 ocean carriers: live vessel positions, ETAs, demurrage alerts.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
15.8% over 79 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
Repository
lxxmng/container-tracking-mcp
GitHub Stars
1
Server Listing
container-tracking-mcp
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct purpose: adding tracking, single-container detail, portfolio summary, demurrage free-time lookup, demurrage risk report, port congestion, and vessel position. The two demurrage tools are explicitly differentiated by their descriptions (carrier free days vs. risk report), so an agent can reliably choose the right one.

Naming Consistency5/5

All tool names use snake_case and follow a consistent verb_noun pattern (add_container, get_container_detail, get_demurrage_free_time, etc.). The single add_ prefix for the creation operation is appropriate and does not break the pattern.

Tool Count5/5

Seven tools is well within the ideal 3-15 range for a container tracking server. Each tool serves a distinct, non-redundant need: tracking setup, status lookup, portfolio overview, demurrage assessment, port congestion, and vessel position.

Completeness4/5

The surface covers the core lifecycle: add tracking, get container details, portfolio summary, demurrage free time and risk report, port congestion, and vessel position. Minor gaps exist (no explicit list_containers or stop/update tracking operation), but agents can typically work around these by using the summary or user-provided container IDs.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 7 tool updates
    • First observedadd_container
    • First observedget_container_detail
    • First observedget_demurrage_free_time
    • First observedget_demurrage_report
    • First observedget_port_congestion
    • First observedget_shipment_summary
    • First observedget_vessel_position

Related MCP Connectors

Related MCP Servers

  • ShippingRates

    vinaybhosle
    A
    license
    Not graded
    quality
    D
    maintenance
    Ocean container shipping intelligence for AI agents — D\&D tariffs, freight rates, vessel schedules, port congestion, inland haulage across 6 major carriers. 24 MCP tools.
    1
    MIT

  • lashing

    devjoinedthechat
    A
    license
    A
    quality
    B
    maintenance
    It enables AI agents to propose and apply container shipment bookings, amendments, and cancellations via DCSA standards, with every write validated, authorized, and logged in a hash-chained ledger. It also provides tracking and schedule lookup tools.
    10
    Apache 2.0

  • ShippingRates MCP Server

    vinaybhosle
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides container shipping intelligence for AI agents, enabling demurrage & detention calculations, local charges, inland haulage rates, and CFS tariffs across multiple shipping lines, with pay-per-request USDC payments via x402.
    -

  • cargotrace-mcp

    AnishaRamanuj
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to track air waybills and ocean containers and compare freight quotes across carriers through typed, validated tools, with normalized milestone timelines, ETAs and check-digit validation.
    1
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources