Skip to main content
Glama
baskcart

W3Ship MCP Server

by baskcart
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to W3Ship MCP Server

No user-submitted related servers found.

    Related Servers

    • digikala-mcp

      stupidprogrammer4
      A
      license
      B
      quality
      B
      maintenance
      Enables product discovery, seller-offer comparison, and bounded, approval-gated cart operations with account-scoped planning and read-back reconciliation.
      40
      MIT

    • W3 Ledger MCP Server

      baskcart
      A
      license
      A
      quality
      C
      maintenance
      Primary purpose is to maintain a self verifying ledger that requires no consesus. Additional features include support for evm compatible and other block chains.
      6
      15 npm
      1
      MIT

    • merx

      kamilkubik89
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to discover products, verify signed catalog feeds, negotiate within published policies, and place mandate-bound orders with signed receipts via MCP, A2A, or REST.
      1
      MIT

    • Witness

      MaximilianoColoma
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides evidence-oriented MCP service for cryptographically identified agents, bounded public contracts, privacy-preserving records, and append-only audit.
      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

    B3.4/5.0

    Scored across 22 tools

    Disambiguation3/5

    Most tools have distinct purposes, but there is some overlap in the commerce flow (e.g., create_cart, add_item, get_cart, delete_cart are clearly related but could be confused for similar operations). The Uniswap tools (check_token_approval, get_swap_quote) are distinct from marketplace tools, but within domains, boundaries are generally clear with descriptions aiding differentiation.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern throughout (e.g., add_item, create_cart, get_listing, remove_listing), with only minor deviations like 'ship_address' (which could be 'get_ship_address' for full consistency). The naming is predictable and readable across all tools.

    Tool Count3/5

    With 22 tools, the count is borderline high for a server covering commerce, marketplace, bookings, and Uniswap integration. It feels slightly heavy, as some tools might be consolidated (e.g., cart operations), but it's not extreme and remains manageable given the broad scope.

    Completeness4/5

    The server covers multiple domains well: commerce (cart CRUD, order creation, payment), marketplace (listing CRUD, search), bookings (slots, bookings), and Uniswap (approval, quotes). Minor gaps exist, such as no tool for updating listings or canceling bookings, but core workflows are supported and agents can work around these omissions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources