Counterparty Mcp Server

Created By
XCP4 months ago
Overview

Counterparty MCP Server

Give AI agents the ability to interact with Counterparty — the token protocol built on Bitcoin. Query balances, assets, orders, and dispensers. Compose, sign, and broadcast transactions. Works with any MCP-compatible client.

npm

Install

No download needed — just add the config below to your AI client. npx fetches and runs the server automatically.

Claude Desktop

Add to claude_desktop_config.json (how to find it):

{
  "mcpServers": {
    "counterparty": {
      "command": "npx",
      "args": ["-y", "@21e14/mcp-server"]
    }
  }
}

Claude Code

claude mcp add counterparty -- npx -y @21e14/mcp-server

With signing (see Signing & Broadcasting):

claude mcp add counterparty \
  -e SIGNER_PRIVATE_KEY=L1aW4aubDFB7yfras2S1mN... \
  -e SIGNER_ADDRESS=bc1q... \
  -- npx -y @21e14/mcp-server

Manage servers with claude mcp list, claude mcp get counterparty, or claude mcp remove counterparty.

VS Code (Copilot)

Use Ctrl+Shift+PMCP: Add ServerStdio, then enter:

npx -y @21e14/mcp-server

Or add to .vscode/mcp.json:

{
  "servers": {
    "counterparty": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@21e14/mcp-server"]
    }
  }
}

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "counterparty": {
      "command": "npx",
      "args": ["-y", "@21e14/mcp-server"]
    }
  }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "counterparty": {
      "command": "npx",
      "args": ["-y", "@21e14/mcp-server"]
    }
  }
}

ChatGPT

In ChatGPT desktop, go to Settings → Beta Features → MCP Servers, then add:

npx -y @21e14/mcp-server

Any MCP Client

The server speaks stdio. Point any MCP-compatible client at:

npx -y @21e14/mcp-server

That's it. The agent can now query the Counterparty network and compose unsigned transactions.

Signing & Broadcasting

To let the agent sign and broadcast transactions, add a signing key:

{
  "mcpServers": {
    "counterparty": {
      "command": "npx",
      "args": ["-y", "@21e14/mcp-server"],
      "env": {
        "SIGNER_PRIVATE_KEY": "L1aW4aubDFB7yfras2S1mN...",
        "SIGNER_ADDRESS": "bc1q..."
      }
    }
  }
}

This enables the sign_and_broadcast tool. Signing gives the AI agent the ability to spend funds — read the security guidance below.

  1. Generate a fresh keypair offline. Don't reuse an existing wallet or generate keys through the AI.
  2. Fund it with only what you're willing to risk. This is your blast radius.
  3. Use a segwit address. P2WPKH (bc1q...), P2SH-P2WPKH (3...), or P2TR (bc1p...). Legacy P2PKH is not supported.
  4. One key, one address. No HD derivation. Counterparty reuses addresses by design.
  5. Keep main holdings elsewhere. The bot wallet is disposable.

Compose-only mode

Without signing keys, the server returns unsigned transaction hex from all compose tools. You can review and sign offline with your own tooling. This is the safest mode.

Transaction verification

sign_and_broadcast extracts and returns the embedded OP_RETURN data from the transaction before signing — done locally without trusting the API, so the agent can verify the transaction matches what was requested.

Environment Variables

VariableRequiredDescription
COUNTERPARTY_NODENoCounterparty node URL (default: https://api.counterparty.io:4000)
SIGNER_PRIVATE_KEYNoWIF-encoded private key for signing
SIGNER_ADDRESSNoBitcoin address for the signing key

Tools

Query (24)

ToolDescription
get_balancesAll token balances for an address
get_balanceSingle asset balance for an address
get_asset_infoAsset metadata (supply, divisibility, issuer)
get_asset_balancesAll holders of an asset
get_assetsSearch/list assets
get_issuancesIssuance history for an asset
get_owned_assetsAssets issued by an address
get_ordersDEX orders
get_orderSingle order by hash
get_order_matchesMatches for an order
get_orders_by_pairOrder book for a trading pair
get_asset_ordersOrders involving an asset
get_address_ordersOrders by address
get_dispensersDispensers
get_dispenserSingle dispenser by hash
get_dispensers_by_assetDispensers for an asset
get_address_dispensersDispensers by address
get_dispensesPurchases from a dispenser
get_dividendsDividend distributions for an asset
get_address_transactionsTransaction history for an address
get_sendsToken transfers from an address
get_transactionSingle transaction by hash
get_utxo_balancesTokens attached to a UTXO
get_latest_blockLatest block info

Compose (18)

ToolDescription
compose_sendSend tokens to an address
compose_mpmaMulti-party multi-asset send
compose_orderPlace a DEX order
compose_cancelCancel an open order
compose_btcpayPay for a matched BTC order
compose_issuanceCreate or update an asset (supports inscriptions)
compose_dispenserCreate, open, or close a dispenser
compose_dispenseBuy from a dispenser
compose_dividendDistribute dividends to holders
compose_broadcastBroadcast a message (supports inscriptions)
compose_sweepSweep all assets to a destination
compose_destroyPermanently burn tokens
compose_fairminterCreate a fair launch (supports inscriptions)
compose_xcp420_fairminterXCP-420 compliant fair launch
compose_fairmintMint from an active fair launch
compose_attachAttach tokens to a UTXO
compose_detachDetach tokens from a UTXO
compose_movetoutxoMove a UTXO to a new output

Bitcoin (4)

ToolDescription
sign_and_broadcastSign and broadcast (requires signing keys)
broadcast_transactionBroadcast an already-signed transaction
get_fee_estimateCurrent fee rate estimate
decode_transactionDecode raw transaction hex

Utility (3)

ToolDescription
unpack_transactionDecode a Counterparty message from a transaction
get_server_infoNode status and version
api_requestRaw API request to any endpoint (full API reference)

Resources

The server includes protocol documentation that agents can read for context:

  • counterparty://protocol-overview — Assets, quantities, DEX, dispensers, fair minting, fees, and operational tips
  • counterparty://xcp420-standard — XCP-420 fair launch standard
  • counterparty://quick-start — Step-by-step workflows for common operations

Development

git clone https://github.com/XCP/mcp-server.git
cd mcp-server
npm install
npm test

Test locally:

{
  "mcpServers": {
    "counterparty": {
      "command": "node",
      "args": ["/path/to/mcp-server/dist/index.js"]
    }
  }
}

License

MIT

Server Config

{
  "mcpServers": {
    "counterparty": {
      "command": "npx",
      "args": [
        "@21e14/mcp-server"
      ]
    }
  }
}
Project Info
Created At
4 months ago
Updated At
2 months ago
Author Name
XCP
Star
-
Language
-
License
-
Category
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago