Connects Claude to LI.FI's cross-chain bridge aggregator so you can query optimal routes for moving crypto between networks. Exposes operations for finding the cheapest or fastest paths, comparing fees across providers, and estimating bridge times. Runs on x402's pay-per-call model where requests cost USDC, so you're not managing API keys or subscriptions. Reach for this when you're building agents that need to advise on multi-chain transfers or automate bridge route selection. The remote SSE transport means it's hosted and ready to use without running your own infrastructure.
Public tool metadata for what this MCP can expose to an agent.
bridge_find_best_routeUse this when you need to bridge tokens between different blockchains. Returns ranked bridge routes with fees and timing in JSON. 1. routes: array of bridge options ranked by best value 2. bridgeProv5 paramsUse this when you need to bridge tokens between different blockchains. Returns ranked bridge routes with fees and timing in JSON. 1. routes: array of bridge options ranked by best value 2. bridgeProv
tokenstringamountstringtoChainstringtoTokenstringfromChainstringBest cross-chain bridge routes via LI.FI -- 60+ chains, 18+ bridges, fees and time compared. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"bridge-routes": {
"url": "https://bridge-routes.api.klymax402.com/mcp"
}
}
}
curl "https://bridge-routes.api.klymax402.com/api/route?fromChain=...&toChain=...&token=...&amount=..."
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
bridge_find_best_route | GET | /api/route | $0.003 | Find the best cross-chain bridge route |
bridge_find_best_routeUse this when you need to bridge tokens between different blockchains. Returns ranked bridge routes with fees and timing in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
fromChain | string | yes | Source chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche) |
toChain | string | yes | Destination chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche) |
token | string | yes | Token symbol to bridge (e.g. USDC, USDT, ETH, WETH) |
amount | string | yes | Amount in smallest unit (e.g. 1000000 for 1 USDC with 6 decimals, 1000000000000000000 for 1 ETH) |
toToken | string | no | Destination token symbol if different from source (optional, defaults to same as token) |
Returns
routes -- array of bridge options ranked by best valuebridgeProvider -- which bridge protocol (Stargate, Across, Hop, Connext, etc.)estimatedTime -- expected bridge completion time in secondsfee -- total bridging fee in USDamountReceived -- expected output amount on destination chainsteps -- detailed step-by-step route (approve, bridge, swap if needed)Example response:
{"routes":[{"bridgeProvider":"Stargate","estimatedTime":60,"fee":0.85,"amountReceived":"999.15","steps":["approve USDC","bridge via Stargate"]}],"fromChain":"Ethereum","toChain":"Base","token":"USDC"}
When to use: moving assets cross-chain to find the cheapest and fastest bridge. Essential for multi-chain portfolio management.
Not for: gas prices (use gas_get_current_price).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT