Skip to main content
Glama
aarondotdev

tracking-requests-mcp

by aarondotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to tracking-requests-mcp

No user-submitted related servers found.

    Related Servers

    • DB2ST MCP

      AlexisMarasigan
      A
      license
      Not graded
      quality
      D
      maintenance
      A horizontally scalable Model Context Protocol server for exposing shipment tracking (and other data sources) as authenticated MCP tools, starting with DB Schenker's public tracking endpoint.
      1
      MIT

    • ShipSmart-MCP

      nia194
      F
      license
      Not graded
      quality
      B
      maintenance
      A standalone MCP server providing shipping tools like address validation and rate previews through a centralized HTTP interface. It serves as the single source of truth for shipping tool behavior across the ShipSmart platform.
      2
      -

    • shiplabel-mcp

      xentral
      A
      license
      A
      quality
      C
      maintenance
      Carrier-agnostic shipping labels as a self-hostable MCP server. Build one shipment request, get a tracking number and a print-ready label back for DHL, DPD, UPS, FedEx, GLS, Sendcloud, and Shipcloud.
      3
      2
      MIT

    • Governed MCP Server

      johannespietsch
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server reference implementation adding enterprise layers (identity, authorization, audit) around MCP, with sample shipment status and delayed shipment tools over a stateless transport.
      Apache 2.0
    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

    A3.6/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools serve distinct purposes: schema checks, commodity lookup, contacts, tracking requests, and label preflight. The only potential confusion is between coverage_report and schema_check, both dealing with schema drift, but their descriptions differentiate them clearly.

    Naming Consistency3/5

    Tool names use snake_case but follow inconsistent patterns: some are noun_verb (commodity_lookup, schema_check), others noun_noun (tracking_requests_list, label_options), and one uses an abbreviation (db_query). This mixed convention reduces predictability.

    Tool Count4/5

    With 9 tools, the server covers core domain operations (commodities, contacts, tracking requests, labels) plus schema introspection. The count is reasonable, though the inclusion of schema tools might be overkill for typical agent interactions.

    Completeness2/5

    The server lacks a label_create tool despite references to it in descriptions, and there are no create/update/delete tools for tracking requests. These gaps will likely cause agent failures when attempting to complete workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources