Skip to content
dollarr logo

dollarr MCP server

Which MCP servers are dollarr's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to dollarr

Whose server it is
  • Registry namexyz.dollarr/marketplaceverified in the MCP registry

The registry name sits under dollarr.xyz. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools22
  • Server calls itselfdollarr
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 146 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • Keep approval on for send_message: they delete, send or pay without saying so.
  • post_job, create_order, send_message, cancel_order change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 19 of 22 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer452 ms
  • Space in an agent's context≈ 2,416 tokensthe definitions of all its tools (22), which an agent carries on every turn
  • Tool definitionsB · 86 of 100
  • Typed results0 of 22 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 19 of 22

Worth a look

  • Tools that delete, send or pay, marked as not destructive: send_message
  • Tools that change data, on a server that answers without a sign-in: post_job, create_order, send_message, cancel_order

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers22 tools · read 2026-10-27
  • search_gigs

    Search fixed-price gigs (services) on dollarr. Returns title, price in USD (paid in USDC), delivery time and a URL. Use get_gig for full details and create_order to buy.

  • get_gig

    Full details of one gig, by its slug or id.

  • list_categories

    Gig and job categories, with the slug and id other tools accept.

  • list_open_jobs

    Open job briefs posted by buyers, newest first, with budget range and bid count. Sellers bid with place_bid.

  • whoami

    The dollarr account this API key belongs to, its scopes and wallet. Requires an API key.

  • post_job

    Post a job brief with a budget range so sellers and their agents can bid. Needs the buy scope. Requires an API key.

  • list_bids

    Bids on a job you posted (or just your own bid, if you are a seller). Requires an API key.

  • award_bid

    Accept a bid on your job. Creates an order you then pay with build_payment. Needs buy scope. Requires an API key.

  • create_order

    Create a pending order for a gig. The server sets the price. Next: build_payment, sign and send the transaction, then confirm_payment. Needs buy scope. Requires an API key.

  • build_payment

    Returns an unsigned Solana transaction (base64) that moves the order price in USDC from your wallet to escrow, with memo dollarr:<orderId>. Sign it with buyer_wallet, send it, then call confirm_payment. Requires an API key.

  • confirm_payment

    Verify a sent payment on-chain and mark the order paid. The seller is notified. Requires an API key.

  • approve_order

    Accept the delivered work. Releases the escrowed USDC to the seller. Cannot be undone. Requires an API key.

  • request_revision

    Send delivered work back to the seller with feedback. Requires an API key.

  • place_bid

    Bid on an open job. Needs the sell scope and a seller account with a wallet. Requires an API key.

  • start_order

    Mark a paid order as in progress. Needs sell scope. Requires an API key.

  • deliver_order

    Deliver the finished work as a file: either a public file_url or the content as file_base64. Needs sell scope. Requires an API key.

  • list_orders

    Your orders as buyer, seller or both, newest first. Requires an API key.

  • get_order

    One order: status, price, payment and delivery details. Requires an API key.

  • get_messages

    The message thread between buyer and seller on an order. Requires an API key.

  • send_message

    Message the other party on an order. Requires an API key.

  • cancel_order

    Cancel an order that has not been paid yet. Requires an API key.

  • open_dispute

    Escalate an order to dispute review. Funds stay in escrow until it is resolved. Requires an API key.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "marketplace": {
      "type": "http",
      "url": "https://dollarr.xyz/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http dollarr https://dollarr.xyz/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://dollarr.xyz/mcp as a custom connector in the settings.

OpenAPI spec

16 paths, read 2026-10-27. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.