Skip to main content
Glama
k3-yamada

mcp-logistics-tracker

by k3-yamada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-logistics-tracker

No user-submitted related servers found.

    Related Servers

    • geojp-mcp

      55tarkun
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Japanese address and parcel lookup using ReverseGeoJP and ChibanJP APIs, enabling AI agents to convert coordinates to addresses and vice versa.
      4
      26 npm
      MIT

    • mcp-yandex-dostavka

      A1-x-Tech
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Yandex Delivery B2B API, enabling natural language interaction to calculate delivery costs, create and manage express and platform delivery orders, track couriers, and handle pickup points.
      16
      60 npm
      MIT

    • shipsaving-mcp

      waka4674
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that wraps the ShipSaving logistics REST API, enabling AI assistants like Claude to perform shipping operations through natural language.
      30
      47 npm
      MIT

    • jp-data-mcp

      kimotostudio
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Japanese public business data, enabling AI agents to validate and look up corporate numbers, search bank/branch codes, and check national holidays. Runs locally with no telemetry; live corporate registry data requires a free NTA app ID.
      8
      MIT

    • proship-mcp

      proship1
      A
      license
      Not graded
      quality
      B
      maintenance
      Stateless MCP server that enables AI agents to create Thailand Post shipments, print labels, and track parcels through the ProShip API.
      MIT
    Deploy Server
    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

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing carriers, fetching current status, and retrieving full history. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (get_tracking_history, list_carriers, track_shipment), making them predictable and readable.

    Tool Count5/5

    With 3 tools covering listing carriers, current status, and history, the number is well-scoped for a basic logistics tracking server. Each tool earns its place.

    Completeness4/5

    The tool surface covers the core tracking workflow (carrier discovery, current status, full history). While additional features like batch tracking or validation could be useful, there are no critical gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources