# Cross-Chain Bridge Route API MCP server

Best cross-chain bridge routes with fees, time, providers. LI.FI-powered. x402.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-br0ski777-bridge-routes
- Repository: https://github.com/Br0ski777/bridge-routes-x402
- Website: https://github.com/Br0ski777/bridge-routes-x402

## Install
- Endpoint: https://bridge-routes.api.klymax402.com/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://bridge-routes.api.klymax402.com/mcp

## Tools
- 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.

1. routes: array of bridge options ranked by best value
2. bridgeProvider: which bridge protocol (Stargate, Across, Hop, Connext, etc.)
3. estimatedTime: expected bridge completion time in seconds
4. fee: total bridging fee in USD
5. amountReceived: expected output amount on destination chain
6. steps: detailed step-by-step route (approve, bridge, swap if needed)

Example output: {"routes":[{"bridgeProvider":"Stargate","estimatedTime":60,"fee":0.85,"amountReceived":"999.15","steps":["approve USDC","bridge via Stargate"]}],"fromChain":"Ethereum","toChain":"Base","token":"USDC"}

Use this BEFORE moving assets cross-chain to find the cheapest and fastest bridge. Essential for multi-chain portfolio management.

Do NOT use for same-chain swaps -- use dex_get_swap_quote instead. Do NOT use for gas prices -- use gas_get_current_price instead. Do NOT use for multi-chain gas comparison -- use crypto_estimate_gas instead. Endpoint: https://bridge-routes.api.klymax402.com/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.Br0ski777
- Version: 1.1.0
- Runtime: Sse
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 16, 2026
- Source: https://registry.modelcontextprotocol.io