MCP for Crypto: How AI Assistants Discover, Quote and Confirm Cross-Chain Swaps

MCP for Crypto: How AI Assistants Discover, Quote and Confirm Cross-Chain Swaps

MCP for Crypto: How AI Assistants Discover, Quote and Confirm Cross-Chain Swaps

MCP for Crypto: How AI Assistants Discover, Quote and Confirm Cross-Chain Swaps

The Model Context Protocol gives an AI assistant a standard way to find a crypto swap tool, ask it for a quote, and hand the final decision back to you before any funds move. Cross-chain demand keeps growing: Chainflip processed $727M in swaps in October 2026, up 17% from $622M in October 2025 (Chainflip Scan). This guide walks through the three steps an assistant takes for a cross-chain swap, using the same quote data you see when you swap native BTC to USDT on Chainflip directly.

What you need

  • An MCP host, meaning an AI app that supports MCP, such as Claude Desktop, Claude Code, Cursor or VS Code.

  • A swap-capable MCP server, or your own integration built on the Chainflip SDK.

  • A wallet holding the asset you want to swap, plus a destination address on the receiving chain.

  • A tab open on Chainflip Scan to follow the swap once it starts.

Step 1: Connect a swap tool your assistant can discover

The official MCP documentation (as served in November 2026) describes MCP as an open-source standard for connecting AI applications to external systems such as data sources, tools and workflows. It compares MCP to a USB-C port for AI applications. Anthropic open-sourced it on 25 November 2024, and on 9 December 2025 the project joined the Agentic AI Foundation under the Linux Foundation for vendor-neutral governance. Claude, ChatGPT, VS Code and Cursor all support it.

The MCP architecture in the current spec revision (2026-07-28) has three roles. The host is the AI app, which coordinates one or more MCP clients, and each client keeps a connection to an MCP server that provides context. Servers run locally over STDIO or remotely over Streamable HTTP, and tools are one of the three core primitives they expose.

What to do: Add a server in your host's MCP settings. A remote server needs an endpoint URL, while a local server needs a command the host can launch. One live option for Chainflip routes is the Broker as a Service MCP server, run by an independent broker at https://chainflip-broker.io/mcp over Streamable HTTP, with no authentication required as of November 2026.

Other integrations exist too. Chainflip's August 2026 recap notes that RAVN shipped an MCP interface on 20 August 2026 so AI agents can route native Bitcoin through Chainflip, calling it "a small thing today". Builders who want their own tooling can wrap the SDK instead, as covered in how to give an AI agent native cross-chain swaps with the Chainflip SDK.

What you will see: Once connected, the client sends a tools/list request and the host shows the tools it found. Per the MCP tools specification (revision 2026-07-28), each tool has a unique name, a description and a JSON Schema for its inputs. Tools are model-controlled, so the model decides when to call them based on your conversation. With the BaaS server you should see tools such as list_assets, get_quotes, start_swap, start_dca_swap and a status check.

Common mistake: Trusting a directory label. Some MCP directories tag the BaaS server as "official", but Chainflip has not published it as an official Chainflip server. Treat it as a third-party broker, and check who runs any server before you connect it.

Step 2: Ask for a quote with exact assets and chains

What to do: Ask in plain language, but be specific, for example "Quote 0.1 BTC on Bitcoin to USDT on Ethereum, sent to this address." The assistant fills in the tool's input schema and sends a tools/call request to a quote tool such as get_quotes. If you plan to sell native BTC for stablecoins, this is the moment to read the numbers rather than the assistant's summary.

What you will see: The assistant returns an expected output amount with the rate, fees and estimated duration. On Chainflip, the SDK's getQuoteV2 provides exactly these fields (expected exchange rate, expected fees and expected duration) as a regular or DCA quote. Each quote comes with recommended slippage tolerance and retry duration values (Chainflip Docs, current SDK v2.x). By default the SDK pulls from the Broker API that Chainflip runs for each network, and integrators can point it at a different broker URL.

Common mistake: Naming a ticker without a chain. USDT is live on Chainflip across Ethereum, Solana, Arbitrum, Polkadot Assethub, Tron and BNB Chain, so "USDT" alone forces the model to guess, and a wrong guess changes the destination network.

Swap BTC to USDT on Chainflip

Step 3: Confirm before anything is sent

What to do: When the assistant moves to start_swap, stop and read the approval prompt. The MCP spec's user interaction model (revision 2026-07-28) says there SHOULD always be a human in the loop who can deny tool invocations. It also recommends that apps show which tools are exposed, flag each invocation clearly and use confirmation prompts. That is a recommendation for hosts and clients, not a rule the protocol enforces, so check your host's approval settings rather than counting on a server to ask.

What you will see: An approval dialog showing the tool name and its arguments: source asset, destination asset, amount and destination address. Once you approve, the BaaS start_swap tool returns a deposit address, and nothing moves until you send funds to it from your own wallet. From there, Chainflip's decentralized custody model takes over, with funds secured by validators and no centralized custodian, and you can follow progress on Chainflip Scan or through the server's status tool.

Common mistake: Clicking "always allow" for swap tools. Auto-approval is fine for read-only tools like list_assets, but approve every call that produces a deposit address and compare the destination address character by character against your wallet.

Troubleshooting

  • No tools appear after connecting. Check the transport: remote servers need the full endpoint URL, and local servers need a working launch command. Restart the host so the client requests the tool list again.

  • The quote differs from the swap app. Quotes are estimates that move with market prices and pool depth. Request a fresh quote and compare it against Chainflip's swap app at the same moment.

  • No approval prompt appeared. Your host likely has auto-approval switched on. Turn it off for execution tools, since the spec only recommends prompts and the setting lives in your host.

  • The assistant says an asset is unsupported. Check the chain first. Chainflip supports BNB and USDT on BNB Chain but not USDC, and cbBTC is supported on Ethereum only.

  • The swap isn't showing yet. Look up the swap or deposit channel on Chainflip Scan. Bitcoin deposits need block confirmations before the swap starts, so allow time before assuming something is wrong.

With MCP, the assistant assembles the cross-chain swap for you: it discovers the tool, fetches a quote with visible rate, fees and duration, and then waits for you. The safety model rests on those last two parts, a transparent quote and a human approving the call, so choose hosts and servers that make both obvious.

To see the mechanics without an assistant in the middle, run the same quote on Chainflip's swap app and compare the numbers. For the bigger picture on user experience, read what changes when AI assistants can execute cross-chain trades.

Resources

  • Swap - Start swapping native assets

  • Lending - Borrow against native Bitcoin

  • Blog - Product updates and announcements

  • Chainflip Scan - Track swaps and network activity

  • Website - Explore Chainflip

Earn with Chainflip:

Find us:

FAQ

What is MCP in crypto?

MCP, the Model Context Protocol, is an open-source standard for connecting AI applications to external tools and data. In crypto, it lets an assistant call swap tools such as asset lists, quotes and swap execution through one common interface instead of a custom integration for every app.

Is there an official Chainflip MCP server?

Chainflip has not published an official MCP server. The options available today are third-party: RAVN shipped an MCP interface for routing native Bitcoin through Chainflip in August 2026, and an independent broker runs the Broker as a Service MCP server. Builders can also wrap the Chainflip SDK in their own tools.

Does MCP force an assistant to ask before it swaps?

No. The MCP spec says there SHOULD be a human in the loop who can deny tool calls and recommends confirmation prompts, but the host app is responsible for enforcing that. Check your host's approval settings and avoid auto-approving execution tools.

Can an AI assistant move my funds on its own?

Not in the deposit-address flow described here. The swap tool returns a deposit address, and nothing happens until you send funds from your own wallet. An assistant can only sign transactions if you give it access to a wallet, so review the quote and destination address yourself before sending.

Get Chainflip updates

Product news, protocol updates, and launches.