W3Ship MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ship_addressB | Securely retrieve a physical address using a public key and a timed cryptographic signature. |
| create_cartA | Create a new TMF663 shopping cart. If W3SHIP_PUBLIC_KEY is configured, it is used automatically — no id required. Otherwise provide an SLH-DSA or ECDSA public key (hex). |
| get_cartA | Retrieve a shopping cart by its Public Key ID. Uses W3SHIP_PUBLIC_KEY if no id is provided. |
| add_itemA | Add an item to an existing shopping cart. Uses W3SHIP_PUBLIC_KEY as cartId if not provided. |
| delete_cartC | Delete a shopping cart. |
| create_orderA | Convert a Shopping Cart into a confirmed Order (TMF622) and initiate fulfillment. |
| get_orderC | Retrieve detailed information about a specific Order (TMF622). |
| track_shipmentC | Track the delivery status of a shipment (TMF621). |
| get_available_slotsA | Get available session time slots for a location on a given date. Returns times, capacity, pricing, and activity type. Works for any bookable service (VR, fitness, dining, salon, etc.). |
| hold_slotA | Hold/reserve a session time slot for a customer. The slot is held for 10 minutes pending payment. Works for any bookable service. |
| list_bookingsB | List all confirmed session bookings. Optionally filter by location or date. |
| generate_demo_keyA | Generate a demo ECDSA key pair for testing. Returns a public key hex that can be used with create_cart and other tools. Useful for trying out the commerce flow without a real wallet. |
| get_identityA | Show the currently configured identity (W3SHIP_PUBLIC_KEY). Returns the public key and its type if set, or instructions on how to configure one. |
| get_swap_quoteA | Get a swap quote from Uniswap. Returns estimated output, routing path, gas fees, and price impact. Supports V2, V3, V4, and UniswapX protocols. Requires UNISWAP_API_KEY env var. |
| check_token_approvalA | Check if a token is approved for swapping on Uniswap. Returns whether approval is needed and the approval transaction if so. Requires UNISWAP_API_KEY env var. |
| create_listingA | Create a P2P marketplace listing. Anyone can sell items — no merchant onboarding needed. Specify title, price, currency (USDC/ETH/etc), and your wallet address for payment. |
| search_listingsA | Browse the W3Ship P2P marketplace. Search by category (electronics, gifts, clothing, etc.) or keyword. Returns active listings with prices and seller info. |
| get_listingB | Get full details of a specific marketplace listing by ID. |
| remove_listingA | Remove a marketplace listing. Only the seller can remove their own listing. |
| confirm_paymentA | Submit an on-chain payment transaction for verification. After paying the seller (send crypto to their wallet address), provide the transaction hash here to verify payment and update the order status to "paid". |
| add_trackingA | Seller tool: Add real shipping tracking info to an order after shipping the item. Provides the buyer with a tracking number and carrier. |
| claim_promoA | Claim a FREE promotional listing. Items are $0. For shipping promos you pay shipping only; for pickup promos it is completely free. One claim per wallet. Must have a registered W3Ship/Dah.mx identity (address required for shipping, wallet-only for pickup). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
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.
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.
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.
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.