Skip to main content
Glama
ebongard

renfield-mcp-tracking

by ebongard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to renfield-mcp-tracking

No user-submitted related servers found.

    Related Servers

    • 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

    • 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
    • Trackmage MCP Server by trackmage

      Trackmage MCP Serverofficial

      trackmage
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides shipment tracking api and logistics management capabilities through the TrackMage API. Enables creation and monitoring of shipments and orders, carrier detection, tracking checkpoint retrieval, and comprehensive logistics workflow automation.
      2
      MIT

    • Parcel MCP Server

      oliverames
      A
      license
      A
      quality
      A
      maintenance
      Enables delivery tracking through the Parcel API, including listing and fetching deliveries, searching carriers, and adding new deliveries with optional write protection and multiple credential methods.
      5
      6 npm
      MIT

    • mcp-logistics-tracker

      k3-yamada
      A
      license
      A
      quality
      D
      maintenance
      MCP server for tracking Japanese logistics carriers (Yamato, Sagawa, Japan Post) via mock or AfterShip adapter. Enables AI agents to query shipment status and history in natural language.
      3
      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.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: carrier detection, listing carriers, and tracking parcels. No overlap in functionality.

    Naming Consistency5/5

    All tools follow a snake_case verb_noun pattern (detect_carrier, list_carriers, track_parcel), with consistent naming. The slight pluralization in list_carriers is natural for listing operations.

    Tool Count5/5

    With only 3 tools, the set is concise yet sufficient for the domain of parcel tracking. Each tool earns its place without unnecessary bloat.

    Completeness5/5

    The tool set covers the core lifecycle: carrier detection (identify carrier from number), carrier discovery (list available carriers), and tracking (get status and events). No obvious gaps for a tracking helper server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources