marketplace

Buy, sell and bid on vote-escrow NFTs and .base.eth names.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    Buy, sell and bid on vote-escrow NFTs and .base.eth names. Non-custodial, settles on Seaport.

    How to connect

    How to connect marketplace to Claude

    The server address to paste into Claude settings:

    https://www.market0x.com/api/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect marketplace to ChatGPT

    The server address to paste into ChatGPT settings:

    https://www.market0x.com/api/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect marketplace to Cursor

    The server address to paste into Cursor settings:

    https://www.market0x.com/api/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (15)

    Raw names from tools/list. Only developers need these.

    list_micro_marketsList the markets this marketplace facilitates (asset, chain, currencies, fee).
    get_listingsActive listings/auctions for a market. Each row carries the ask and the position's underlying contents priced at current market (published formula: /docs#data-sources), plus discountPct (the difference between them). Sorted by discount percentage, descending.
    get_listing_detailsFull detail for one order including a FRESH live-contents snapshot (principal, claimable rewards, voting/earning power, as_of_block).
    get_recent_tradesRecently settled sales for a market. `amount` is the EXACT settled total (incl. fee) from the on-chain fill where the indexer recorded it, with `settledAt` the block time and `exact: true`; otherwise it falls back to the listed ask with `exact: false` (a decayed Dutch auction settles BELOW its listed amount, so treat inexact rows as an upper bound).
    prepare_purchasePrepare the non-custodial transaction package to BUY a listing (or accept an offer): ordered approvals + Seaport fulfillOrder calldata + a fresh contents snapshot. prepared.summary quotes the CURRENT price (Dutch auctions interpolate, asOf says when); the approval grants approveBaseUnits — slightly above the quote on a decaying order, never above maxTotalBaseUnits — and Seaport charges the exact interpolated amount at fill. On auctions, prepared.cleanup is an optional post-settlement tx that zeroes the residual allowance. The agent's own wallet signs and submits — this never signs or holds keys.
    prepare_offerPrepare a BID/offer on a position: returns the Seaport order to sign (EIP-712), the currency approval needed, and how to submit it. Name markets (basenames) take `name` instead of tokenId — any REGISTERED name is biddable, listed or not. The agent reads its Seaport counter, signs, and POSTs the signed order — settlement stays on Seaport.
    prepare_listingPrepare a SELL listing or Dutch auction. Verifies the seller OWNS the position and it's transferable (not voted/attached), builds the Seaport order with the Interface fee injected by the server, and returns the one-time NFT approval + EIP-712 typed data to sign. Name markets (basenames) take `name` instead of tokenId. Never signs or holds keys.
    prepare_cancelPrepare the on-chain Seaport cancel transaction for an active order. Only the order's offerer can execute it (Seaport enforces msg.sender == offerer), so the calldata is safe to return. After it confirms, POST { txHash } to the confirm endpoint to update the book.
    get_ordersList orders created by an address (its listings, auctions, offers). Status is reconciled by the background worker — treat as advisory until checked at fill.
    get_owned_positionsList the positions an address owns in a market, with listability (voted/attached positions can't transfer).
    subscribe_notificationsSubscribe a wallet to push notifications (order_filled / offer_received / saved_search) via an HMAC-signed webhook — the agent-native alternative to polling. Two-step: call WITHOUT `signature` to get the exact message to sign (EIP-191 personal_sign), then call again WITH the signature. `chainId` is signed over and the signature is verified on THAT chain, so pass the chain the wallet actually signs on (smart-wallet signatures do not validate cross-chain). Each signed message is SINGLE-USE: resending the same body returns 409 replayed_signature — retry with a fresh timestamp and a new signature. The response includes the webhook HMAC secret ONCE (verify x-market0x-signature = hex(HMAC-SHA256(rawBody, secret))).
    search_namesSearch the Basenames REGISTRY — every registered name, listed or not — by substring, length, character class and trait, with each row's owner, expiry and (when for sale) its order hash. This is the discovery surface for `prepare_offer`, which can bid on any registered name whether or not it is listed; without it an agent has no way to learn a name exists. Name markets only.
    prepare_finalizePrepare the post-purchase FINALIZE transactions for a Basename you now own: reclaim management rights, set the resolver, and point the name at your address (optionally set it as your primary name). A sale transfers the NFT but NOT the ENS registry management — until reclaim runs, the PREVIOUS owner can still change the name's resolver and records. Run this straight after a fill. Returns ordered calldata; the agent's own wallet signs and submits, and every call is msg.sender-enforced on-chain so the package is only usable by the owner.
    list_subscriptionsList a wallet's notification subscriptions (webhook URLs redacted to origin).
    unsubscribe_notificationsDelete a notification subscription. Two-step like subscribe_notifications: call without `signature` to get the message to sign. `chainId` is signed over and verified on that chain. Signed messages are single-use.