Skip to main content
Glama

Related Servers

Alternatives to alopeyk-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      71 npm
      MIT
    • A
      license
      A
      quality
      C
      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
    • 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
      13 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for the Yango Delivery B2B API, enabling price estimation, express-courier claim creation and confirmation, courier tracking, and recipient tracking links through natural language.
      13
      81 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Production-ready MCP server for AI agents — web search, content extraction, screenshots, weather, finance, email validation, translation, and IP geolocation.
      6 npm
      6
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Connect any MCP-compatible AI to Royal Mail shipping. This server exposes five tools that let Claude, Cursor or any MCP client book orders, fetch postage labels, track shipments and cancel bookings through the official Click & Drop API.
      5
      10 npm
      3
      MIT

    TDQS

    A3.9/5.0

    Scored across 34 tools

    Disambiguation5/5

    Tools are clearly separated by prefix (alopeyk_ vs alonomic_) and each has a distinct purpose. Even within groups, tools like alopeyk_get_price and alopeyk_get_batch_price are well-differentiated. Overlap is minimal.

    Naming Consistency4/5

    The majority follow a verb_noun pattern with consistent prefixes. However, a few tools (healthcheck, list_instances, alopeyk_payment_route, alopeyk_print_invoice_url) break the pattern, causing minor inconsistency.

    Tool Count4/5

    34 tools is on the higher side but reasonable for a server covering two distinct service APIs with full CRUD and utility operations. Each tool earns its place without unnecessary duplication.

    Completeness3/5

    The tool set covers core operations for both Alopeyk and Alonomic services, but lacks listing tools for orders and parcels. Agents cannot retrieve a list of existing orders or parcels, which is a notable gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues