Crypto APIs MCP Broadcast
OfficialAllows broadcasting signed Bitcoin transactions to the blockchain.
Allows broadcasting signed Bitcoin Cash transactions to the blockchain.
Allows broadcasting signed Dash transactions to the blockchain.
Allows broadcasting signed Dogecoin transactions to the blockchain.
Allows broadcasting signed Ethereum transactions to the blockchain.
Allows broadcasting signed Litecoin transactions to the blockchain.
Allows broadcasting signed Optimism transactions to the blockchain.
Allows broadcasting signed Polygon transactions to the blockchain.
Allows broadcasting signed Zcash transactions to the blockchain.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Crypto APIs MCP Broadcast Broadcast signed ETH tx 0xf86b... to mainnet"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@cryptoapis-io/mcp-broadcast
MCP server for Crypto APIs Broadcast product. Submit locally signed transactions to the blockchain.
API Version: Compatible with Crypto APIs version 2024-12-12
Features
Broadcast signed transaction hex to any supported blockchain
Supports EVM (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron)
Supports UTXO (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash)
Works with transactions signed by
@cryptoapis-io/mcp-signeror any external signer
Related MCP server: Blockchain Payment MCP Server
Prerequisites
Node.js 18+
Crypto APIs account and API key (sign up | get API key)
Installation
npm install @cryptoapis-io/mcp-broadcastOr install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
Usage
# Run with API key
npx @cryptoapis-io/mcp-broadcast --api-key YOUR_API_KEY
# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-broadcast
# HTTP transport (listens on 127.0.0.1; see "Exposing the server beyond localhost")
npx @cryptoapis-io/mcp-broadcast --transport http --port 3000 --api-key YOUR_API_KEYClaude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"cryptoapis-broadcast": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-broadcast"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"cryptoapis-broadcast": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-broadcast"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}MCP Inspector
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-broadcast --api-key YOUR_API_KEYn8n
Start the server in HTTP mode:
npx @cryptoapis-io/mcp-broadcast --transport http --port 3000 --api-key YOUR_API_KEYIn your n8n workflow, add an AI Agent node
Under Tools, add an MCP Client Tool and set the URL to
http://localhost:3000/mcp
n8n in Docker:
localhostinside the container is not your machine. Start the server with--host 0.0.0.0andMCP_AUTH_TOKENset (see Exposing the server beyond localhost), usehttp://host.docker.internal:3000/mcpas the URL, and add anAuthorization: Bearer <token>header to the MCP Client Tool credential.
All servers default to port 3000. Use
--portto assign different ports when running multiple servers.
Available Tools
broadcast_signed_transaction
Submit a signed transaction to the blockchain.
Parameter | Description |
| Target blockchain (ethereum, bitcoin, binance-smart-chain, tron, polygon, etc.) |
| Network (mainnet, testnet, sepolia, mordor, nile, amoy, fuji, etc.) |
| The signed transaction hex string to broadcast |
CLI Arguments
Argument | Description | Default |
| Crypto APIs API key |
|
| Transport type: |
|
| HTTP host (use |
|
| Bearer token callers must send ( |
|
| Comma-separated | — |
| HTTP port |
|
| HTTP path |
|
| Enable stateless HTTP mode |
|
HTTP API Key Modes
When using HTTP transport, the server supports two API key modes:
With
--api-key: The key is used for all requests.x-api-keyrequest headers are ignored.Without
--api-key: Each request must include anx-api-keyheader with a valid Crypto APIs key. This enables hosting a public server where each user provides their own key.
# Per-request key mode (multi-tenant)
npx @cryptoapis-io/mcp-broadcast --transport http --port 3000
# Clients send x-api-key header with each requestExposing the server beyond localhost
HTTP mode listens on 127.0.0.1 by default, so only processes on the same machine can reach it.
To accept connections from other machines or containers, bind explicitly and protect the port:
# Startup-key mode: callers must present the token (the server refuses to start without one)
export MCP_AUTH_TOKEN=$(openssl rand -hex 32)
npx @cryptoapis-io/mcp-broadcast --transport http --host 0.0.0.0 --port 3000 --api-key YOUR_API_KEY \
--allowed-hosts mcp.internal.example
# Clients send: Authorization: Bearer $MCP_AUTH_TOKEN
# Per-request key mode: no startup key, every request must carry the caller's own x-api-key
npx @cryptoapis-io/mcp-broadcast --transport http --host 0.0.0.0 --port 3000--allowed-hosts restricts the Host header (DNS rebinding protection) when not bound to loopback. Prefer MCP_AUTH_TOKEN over --auth-token: command-line arguments are visible in the process list.
Stdio transport always requires an API key at startup.
Important: API Key Required
Warning: Making requests without a valid API key — or with an incorrect one — may result in your IP being banned from the Crypto APIs ecosystem. Always ensure a valid API key is configured before starting any server.
Remote MCP Server
Crypto APIs provides an official remote MCP server with all tools available via HTTP Streamable transport at https://ai.cryptoapis.io/mcp. Pass your API key via the x-api-key header — no installation required.
License
MIT
Available Tools
2 toolsbroadcast_signed_transactionBroadcast signed transactionADestructive
Broadcast locally signed transaction (Broadcast product).
Submit a signed transaction hex to the network. Supported blockchains and networks vary; see credits for per-chain cost.
Note: 'broadcast-signed-transaction' actions require confirmation. They return a preview with a one-time token instead of executing immediately.
Credits by action (source: OpenAPI): • broadcast-signed-transaction: arbitrum 80, avalanche 90, base 60, binance-smart-chain 125, bitcoin 50, bitcoin-cash 60, dash 55, dogecoin 55, ethereum 50, ethereum-classic 65, litecoin 55, optimism 70, polygon 100, solana 150, tezos 65, tron 75, xrp 50, zcash 65
Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
Inputs: network (required), blockchain (required), signedTransactionHex (required), context, +1 more.
system_infoCryptoAPIs reference infoARead-onlyIdempotent
CryptoAPIs reference documentation — no API call, no credits consumed.
Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior
Inputs: action (required), context.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
broadcast_signed_transaction and system_info have clearly distinct purposes: one performs a network action, the other returns static reference documentation. There is no realistic overlap or misselection risk.
Both names use snake_case and are readable, but they follow different patterns: broadcast_signed_transaction is verb-led while system_info is noun-led. This is a minor deviation from a single verb_noun convention.
Only two tools are exposed; one is the sole operational action and the other is a documentation meta-tool. This is thin for a server, though it may match the narrow Broadcast product scope.
The surface covers submitting a signed transaction and reference lookup, but there is no tool to confirm the preview token or query broadcast/transaction status. That leaves the confirmation workflow and result tracking as potential dead ends.
Maintenance
Related MCP Connectors
Quote, create and track crypto swaps across hundreds of coins and networks. No account needed.
Read chain data on 200+ networks and Sui: transactions, logs, balances, objects, ABI-decoded.
Keyless, read-only BNB Chain and Ethereum data: transactions by hash, tokens with a lookalike check
Explore blockchain data across addresses, tokens, blocks, and transactions. Investigate any transa…
Related MCP Servers
AlicenseBqualityDmaintenanceProvides access to Tatum's blockchain API across 40+ networks, enabling developers to interact with blockchain data, manage notifications, estimate fees, access RPC nodes, and work with smart contracts through natural language.3166 npm15MIT- AlicenseNot gradedqualityDmaintenanceEnables blockchain payment operations across multiple networks including Base, Ethereum, BSC, Polygon, and Avalanche. Supports balance queries, token transfers, transaction tracking, wallet management, and gas fee estimation with built-in security limits.MIT
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Prepare Transactions product that builds unsigned EVM transactions for native coin, fungible token (ERC-20), and NFT (ERC-721) transfers.8305 npmMIT
- AlicenseAqualityBmaintenanceMCP server for local transaction signing across EVM, UTXO, Tron, and XRP blockchains, with no network calls or API keys required.7425 npmMIT