CrossFin MCP Server

CrossFin MCP server exists for a simple reason — assistants are far more useful when they can act on CrossFin directly instead of describing what you should do. AI agent access to Asian crypto markets. Korean exchange routing and x402 paid APIs.

What you get

CrossFin is a financial router for AI agents. It finds the cheapest path to move money across 14 exchanges (Bithumb, Upbit, Coinone, GoPax, bitFlyer, WazirX, bitbank, Indodax, Bitkub, Binance, OKX, Bybit, KuCoin, Coinbase), pays for APIs with crypto (x402 protocol), and gives agents real-time access to market data that's normally locked behind Korean-language interfaces and IP restrictions.

What the assistant can call

Once CrossFin is connected, these are the calls the assistant has available:

• find_optimal_route — Optimal crypto transfer path across 14 exchanges (free)
• list_exchange_fees — Trading + withdrawal fee comparison
• compare_exchange_prices — Live Bithumb KRW vs Binance USD comparison
• get_kimchi_premium — Korean vs. global route spread (free preview)
• search_services — Search registered services
• get_guide — Full agent guide (services, payment flow, examples)
• call_paid_service — Call any paid API with automatic x402 payment
• create_wallet — Local ledger wallet
• get_balance — Check wallet balance
• transfer — Transfer between wallets
• list_transactions — Transaction history
• set_budget — Daily spend limit

Configuration and credentials

You will need one environment variable: EVM_PRIVATE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. CrossFin's toolset — find_optimal_route, list_exchange_fees, compare_exchange_prices and 11 more — is a fair guide to whether it matches your workflow. It is maintained by bubilife1202; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch CrossFin.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the crossfin mcp server does with a few real requests.