
XCP
io.github.XCPPublished by GitHub account XCPv1.0.1Updated Oct 25, 2026
Interact with Counterparty — the token protocol on Bitcoin. Query, compose, sign.
Overview
A local MCP server that lets an assistant query the Counterparty token protocol on Bitcoin and compose, sign and broadcast transactions.
- What you can do
- Query balances, assets, issuances, holders and owned assets for addresses and tokens.Explore DEX orders, order books, order matches, dispensers, dispenses, dividends, sends and transaction history.Build unsigned transactions for sends, multi-asset sends, orders, cancellations, BTC payments, issuances, dispensers, dividends, broadcasts, sweeps, burns, fair launches and UTXO attach/detach/move.Sign and broadcast transactions, broadcast pre-signed ones, estimate fees and decode raw transaction hex.Decode Counterparty messages, check node status and make raw API requests; read bundled protocol, XCP-420 and quick-start documentation.
- When to use it
- Use it when you want an assistant to inspect Counterparty assets, markets and dispensers, or to prepare and optionally send Counterparty transactions on Bitcoin. Compose-only mode suits users who want unsigned transaction hex to review and sign with their own tooling.
- Requirements
- Runs locally via npx (Node.js) over stdio in a desktop MCP client. Optional environment variables: COUNTERPARTY_NODE (defaults to a public Counterparty API node), and SIGNER_ADDRESS plus SIGNER_PRIVATE_KEY for signing. Network access to the Counterparty node is needed.
Installation
In SourceWeft
- Open XCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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.
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):
Claude Code
With signing (see Signing & Broadcasting):
Manage servers with claude mcp list, claude mcp get counterparty, or claude mcp remove counterparty.
VS Code (Copilot)
Use Ctrl+Shift+P → MCP: Add Server → Stdio, then enter:
Or add to .vscode/mcp.json:
Cursor
Add to .cursor/mcp.json:
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
ChatGPT
In ChatGPT desktop, go to Settings → Beta Features → MCP Servers, then add:
Any MCP Client
The server speaks stdio. Point any MCP-compatible client at:
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:
This enables the sign_and_broadcast tool. Signing gives the AI agent the ability to spend funds — read the security guidance below.
Bot wallet pattern (recommended)
- Generate a fresh keypair offline. Don't reuse an existing wallet or generate keys through the AI.
- Fund it with only what you're willing to risk. This is your blast radius.
- Use a segwit address. P2WPKH (
bc1q...), P2SH-P2WPKH (3...), or P2TR (bc1p...). Legacy P2PKH is not supported. - One key, one address. No HD derivation. Counterparty reuses addresses by design.
- 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
Tools
Query (24)
Compose (18)
Bitcoin (4)
Utility (3)
Resources
The server includes protocol documentation that agents can read for context:
counterparty://protocol-overview— Assets, quantities, DEX, dispensers, fair minting, fees, and operational tipscounterparty://xcp420-standard— XCP-420 fair launch standardcounterparty://quick-start— Step-by-step workflows for common operations
Development
Test locally:
License
MIT
Source: README.md at commit 7391d71
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts