Interact with Counterparty — the token protocol on Bitcoin. Query, compose, sign.
{
"mcpServers": {
"counterparty": {
"args": [
"-y",
"@21e14/mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Interact with Counterparty — the token protocol on Bitcoin. Query, compose, sign.
Is it safe?
No known CVEs for @21e14/mcp-server.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 56 days ago. 29 weekly downloads.
Will it work with my client?
Transport: stdio, sse, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@21e14/mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
MCP server for Robokassa payment API — generate payment URLs, check invoice status. First MCP for R
MCP server for Financial Modeling Prep API with 250+ financial data tools
Non-custodial x402 payments for AI agents. Sign locally, spend limits, Base network.
MCP Security Weekly
Get CVE alerts and security updates for Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
No download needed — just add the config below to your AI client. npx fetches and runs the server automatically.
Add to claude_desktop_config.json (how to find it):
{
"mcpServers": {
"counterparty": {
"command": "npx",
"args": ["-y", "@21e14/mcp-server"]
}
}
}
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.
Use Ctrl+Shift+P → MCP: Add Server → Stdio, then enter:
npx -y @21e14/mcp-server
Or add to .vscode/mcp.json:
{
"servers": {
"counterparty": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@21e14/mcp-server"]
}
}
}
Add to .cursor/mcp.json:
{
"mcpServers": {
"counterparty": {
"command": "npx",
"args": ["-y", "@21e14/mcp-server"]
}
}
}
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"counterparty": {
"command": "npx",
"args": ["-y", "@21e14/mcp-server"]
}
}
}
In ChatGPT desktop, go to Settings → Beta Features → MCP Servers, then add:
npx -y @21e14/mcp-server
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.
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.
bc1q...), P2SH-P2WPKH (3...), or P2TR (bc1p...). Legacy P2PKH is not supported.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.
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.
| Variable | Required | Description |
|----------|----------|-------------|
| COUNTERPARTY_NODE | No | Counterparty node URL (default: https://api.counterparty.io:4000) |
| SIGNER_PRIVATE_KEY | No | WIF-encoded private key for signing |
| SIGNER_ADDRESS | No | Bitcoin address for the signing key |