Counterparty Mcp Server

Name: Counterparty Mcp Server
Author: XCP

@XCP

Repository

About Counterparty Mcp Server

Counterparty MCP Server - AI agent access to the Counterparty protocol

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Counterparty MCP Server?

An MCP server that gives AI agents the ability to interact with Counterparty — the token protocol built on Bitcoin. It enables querying balances, assets, orders, and dispensers, as well as composing, signing, and broadcasting transactions. Works with any MCP-compatible client.

How to use Counterparty MCP Server?

No download needed — add the configuration to your MCP client. For most clients, use npx -y @21e14/mcp-server as the command. Optionally set environment variables SIGNER_PRIVATE_KEY and SIGNER_ADDRESS to enable signing and broadcasting. The server then exposes 49 tools and 3 resources for agent interaction.

Key features of Counterparty MCP Server

24 query tools for reading blockchain data
18 compose tools for building transactions
4 Bitcoin tools including signing and broadcasting
3 utility tools for debugging and raw API access
Built-in protocol documentation for agent context
Works with Claude, VS Code, Cursor, ChatGPT, and more

Use cases of Counterparty MCP Server

Check token balances for any Bitcoin address
Place or cancel orders on the Counterparty DEX
Create and manage token dispensers
Issue new assets or launch fair mints
Automate token sends and sweeps across addresses

FAQ from Counterparty MCP Server

What is the default Counterparty node URL?

The default node URL is https://api.counterparty.io:4000. You can override it with the COUNTERPARTY_NODE environment variable.

How do I enable signing and broadcasting?

Set SIGNER_PRIVATE_KEY (WIF-encoded) and SIGNER_ADDRESS (segwit address) in the server’s environment. This activates the sign_and_broadcast tool.

Which Bitcoin address types are supported for signing?

P2WPKH (bc1q...), P2SH-P2WPKH (3...), and P2TR (bc1p...) are supported. Legacy P2PKH is not supported.

What happens if I don’t provide signing keys?

The server runs in compose-only mode: all compose tools return unsigned transaction hex. You can review and sign offline with your own tooling.

Where are the Counterparty protocol docs located for agents?

The server exposes three resources: counterparty://protocol-overview, counterparty://xcp420-standard, and counterparty://quick-start. Agents can read these for context.