MCP · STREAMABLE HTTP · NO KEY

Crypto Mixer MCP Server

Let an AI agent mix Bitcoin, Ethereum, BNB and Solana for you. Automated code in the cloud runs every step on its own, through five plain tools: check fees, start a mix, report coins sent, follow the status, save the Letter of Guarantee.

Connect Your AI Agent

Endpoint: https://bitcoinmix.io/mcp. Transport: Streamable HTTP. No sign-in.

Claude Code

claude mcp add --transport http crypto-mixer https://bitcoinmix.io/mcp

Claude Desktop, Cursor, VS Code

Add the endpoint to the client’s MCP settings file:

{
  "mcpServers": {
    "crypto-mixer": {
      "type": "http",
      "url": "https://bitcoinmix.io/mcp"
    }
  }
}

MCP Tools

Tool	What It Does	Changes Anything
`get_mixer_info`	Supported coins and networks, minimum amounts, confirmations, the random service fee range and the delay range.	No
`create_mix`	Start a mix of BTC, ETH, BNB or SOL.	Yes
`get_mix_status`	Status of one mix: amount received, the payout, fees and timing.	No
`notify_coins_sent`	Tell the mixer the coins were sent so send_to_address is checked at +1, +5 and +10 minutes.	Yes
`get_letter_of_guarantee`	The Letter of Guarantee for one mix as plain text.	No

A Mix Step by Step

get_mixer_info: minimums, the fee range and the delay range.
create_mix: coin, receiving address and a delay from 30 to 1,200 minutes. Returns the one-time send_to_address and the mix_id.
The user sends at least the minimum from their own wallet.
notify_coins_sent: the address is checked at +1, +5 and +10 minutes.
get_mix_status until it reads complete. Fresh coins are then at the receiving address.

Example Tool Call

POST https://bitcoinmix.io/mcp
Content-Type: application/json
Accept: application/json, text/event-stream

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_mix",
    "arguments": {
      "coin": "SOL",
      "receiving_address": "9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM",
      "delay_minutes": 45
    }
  }
}

The result holds the same fields as the crypto mixer API, as text and as structured content. A refusal, such as an invalid address, comes back as a tool error with a code and a sentence the agent can act on.

Supported Coins

Bitcoin mixer: Bitcoin network, minimum 0.0015 BTC
Ethereum mixer: Ethereum mainnet, minimum 0.05 ETH
BNB mixer: BNB Smart Chain, minimum 0.15 BNB
Solana mixer: Solana mainnet, minimum 1 SOL

Keeping a Mix Private

The mix id is the only key to a mix. The agent should keep it private.
Never share a seed phrase or private key. The automated code never asks for one.
Send from an address you control, so a refund stays possible.
Save the Letter of Guarantee until the mix reads complete.

MCP Server FAQ

What Is a Crypto Mixer MCP Server?

MCP is the standard way AI agents call tools. Here the tools run as automated code in the cloud: an agent starts a Bitcoin, Ethereum, BNB or Solana mix, checks on it and fetches its Letter of Guarantee in plain language.

Does the MCP Server Need an API Key or OAuth?

No. The automated code is open to any MCP client over Streamable HTTP. Each mix is reached only through its own 64-character mix id, returned by create_mix.

Which AI Agents Can Use the Mixer MCP Server?

Any MCP client that connects over HTTP: Claude Desktop, Claude Code, Cursor, VS Code and most agent frameworks. Clients without MCP can use the JSON API instead.

Can the Agent Send the Coins Itself?

No. The agent returns the one-time address and the amount. The coins are sent from a wallet the user controls.