mcpField
B
Bridge Routes X402

Bridge Routes X402

Remote
github.comDeveloper Tools0Updated 8w ago

About Bridge Routes X402

Bridge Routes X402 uses LI.FI to find and rank cross-chain asset transfer routes by fees and estimated time. It is designed for AI agents and supports per-call payment in USDC on Base.

Key features

  1. 01Find cross-chain bridge routes
  2. 02Rank routes by value
  3. 03Return fees and estimated times
  4. 04Provide step-by-step route details
  5. 05Pay per call with x402

Use cases

  1. 01Compare costs and timing for cross-chain transfers
  2. 02Find a route for moving assets between chains
  3. 03Review bridge steps and estimated output

MCP support

It provides a remote MCP server exposing the `bridge_find_best_route` tool to clients. The HTTP API also supports x402 per-call payment in USDC on Base.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://bridge-routes.api.klymax402.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Cross-Chain Bridge Route API

MCP Server x402 License: MIT

Best 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.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "bridge-routes": {
      "url": "https://bridge-routes.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

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.

Tools

ToolMethodPathPriceDescription
bridge_find_best_routeGET/api/route$0.008Find the best cross-chain bridge route
bridge_find_best_routePOST/api/route$0.008Find the best cross-chain bridge route (POST variant)
bridge_find_best_route

Use this when you need to bridge tokens between different blockchains. Returns ranked bridge routes with fees and timing in JSON.

Parameters

NameTypeRequiredDescription
fromChainstringyesSource chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche)
toChainstringyesDestination chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche)
tokenstringyesToken symbol to bridge (e.g. USDC, USDT, ETH, WETH)
amountstringyesAmount in smallest unit (e.g. 1000000 for 1 USDC with 6 decimals, 1000000000000000000 for 1 ETH)
toTokenstringnoDestination token symbol if different from source (optional, defaults to same as token)

Returns

  • routes -- array of bridge options ranked by best value
  • bridgeProvider -- which bridge protocol (Stargate, Across, Hop, Connext, etc.)
  • estimatedTime -- expected bridge completion time in seconds
  • fee -- total bridging fee in USD
  • amountReceived -- expected output amount on destination chain
  • steps -- 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).

bridge_find_best_route

Use this when you need to bridge tokens between different blockchains. Returns ranked bridge routes with fees and timing in JSON. POST variant of bridge_find_best_route -- same params passed as JSON body instead of query string.

Parameters

NameTypeRequiredDescription
fromChainstringyesSource chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche)
toChainstringyesDestination chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche)
tokenstringyesToken symbol to bridge (e.g. USDC, USDT, ETH, WETH)
amountstringyesAmount in smallest unit (e.g. 1000000 for 1 USDC with 6 decimals, 1000000000000000000 for 1 ETH)
toTokenstringnoDestination token symbol if different from source (optional, defaults to same as token)

Returns

  • routes -- array of bridge options ranked by best value
  • bridgeProvider -- which bridge protocol (Stargate, Across, Hop, Connext, etc.)
  • estimatedTime -- expected bridge completion time in seconds
  • fee -- total bridging fee in USD
  • amountReceived -- expected output amount on destination chain
  • steps -- 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).

Example agent prompts

  • "Bridge tokens between different blockchains"
  • "Bridge tokens between different blockchains"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.