{
  "markdown": "# @cryptoapis-io/mcp-broadcast\n\nMCP server for [Crypto APIs](https://cryptoapis.io/) Broadcast product. Submit locally signed transactions to the blockchain.\n\n> **API Version:** Compatible with Crypto APIs version **2024-12-12**\n\n## Features\n\n- Broadcast signed transaction hex to any supported blockchain\n- Supports EVM (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron)\n- Supports UTXO (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash)\n- Works with transactions signed by `@cryptoapis-io/mcp-signer` or any external signer\n\n## Prerequisites\n\n- Node.js 18+\n- [Crypto APIs](https://cryptoapis.io/) account and API key ([sign up](https://app.cryptoapis.io/signup) | [get API key](https://app.cryptoapis.io/api-keys))\n\n## Installation\n\n```bash\nnpm install @cryptoapis-io/mcp-broadcast\n```\n\nOr install all Crypto APIs MCP servers: `npm install @cryptoapis-io/mcp`\n\n## Usage\n\n```bash\n# Run with API key\nnpx @cryptoapis-io/mcp-broadcast --api-key YOUR_API_KEY\n\n# Or use environment variable\nexport CRYPTOAPIS_API_KEY=YOUR_API_KEY\nnpx @cryptoapis-io/mcp-broadcast\n\n# HTTP transport\nnpx @cryptoapis-io/mcp-broadcast --transport http --port 3000 --api-key YOUR_API_KEY\n```\n\n### Claude Desktop\n\nAdd to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS, `%APPDATA%\\Claude\\claude_desktop_config.json` on Windows):\n\n```json\n{\n  \"mcpServers\": {\n    \"cryptoapis-broadcast\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@cryptoapis-io/mcp-broadcast\"],\n      \"env\": {\n        \"CRYPTOAPIS_API_KEY\": \"your_api_key_here\"\n      }\n    }\n  }\n}\n```\n\n### Cursor\n\nAdd to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):\n\n```json\n{\n  \"mcpServers\": {\n    \"cryptoapis-broadcast\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@cryptoapis-io/mcp-broadcast\"],\n      \"env\": {\n        \"CRYPTOAPIS_API_KEY\": \"your_api_key_here\"\n      }\n    }\n  }\n}\n```\n\n### MCP Inspector\n\n```bash\nnpx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-broadcast --api-key YOUR_API_KEY\n```\n\n### n8n\n\n1. Start the server in HTTP mode:\n   ```bash\n   npx @cryptoapis-io/mcp-broadcast --transport http --port 3000 --api-key YOUR_API_KEY\n   ```\n2. In your n8n workflow, add an **AI Agent** node\n3. Under **Tools**, add an **MCP Client Tool** and set the URL to `http://localhost:3000/mcp`\n\n> All servers default to port 3000. Use `--port` to assign different ports when running multiple servers.\n\n## Available Tools\n\n### `broadcast_signed_transaction`\n\nSubmit a signed transaction to the blockchain.\n\n| Parameter | Description |\n|-----------|-------------|\n| `blockchain` | Target blockchain (ethereum, bitcoin, binance-smart-chain, tron, polygon, etc.) |\n| `network` | Network (mainnet, testnet, sepolia, mordor, nile, amoy, fuji, etc.) |\n| `signedTransactionHex` | The signed transaction hex string to broadcast |\n\n## CLI Arguments\n\n| Argument | Description | Default |\n|----------|-------------|---------|\n| `--api-key` | Crypto APIs API key | `CRYPTOAPIS_API_KEY` env var |\n| `--transport` | Transport type: `stdio` or `http` | `stdio` |\n| `--host` | HTTP host | `0.0.0.0` |\n| `--port` | HTTP port | `3000` |\n| `--path` | HTTP path | `/mcp` |\n| `--stateless` | Enable stateless HTTP mode | `false` |\n\n### HTTP API Key Modes\n\nWhen using HTTP transport, the server supports two API key modes:\n\n- **With `--api-key`:** The key is used for all requests. `x-api-key` request headers are ignored.\n- **Without `--api-key`:** Each request must include an `x-api-key` header with a valid Crypto APIs key. This enables hosting a public server where each user provides their own key.\n\n```bash\n# Per-request key mode (multi-tenant)\nnpx @cryptoapis-io/mcp-broadcast --transport http --port 3000\n# Clients send x-api-key header with each request\n```\n\n> Stdio transport always requires an API key at startup.\n\n## Important: API Key Required\n\n> **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.\n\n## Remote MCP Server\n\nCrypto APIs provides an official remote MCP server with all tools available via HTTP Streamable transport at [https://ai.cryptoapis.io/mcp](https://ai.cryptoapis.io/mcp). Pass your API key via the `x-api-key` header — no installation required.\n\n## License\n\nMIT\n",
  "bytes": 4410,
  "sha": "215639a3aa4ab05210f0d247d271b8ff22a565a007c10a61b827222dc2bb6f06",
  "repo_slug": "cryptoapis-io/cryptoapis-mcp-broadcast",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_cryptoapis_io_mcp_broadcast_504c8434/readme"
}