Cross-Chain Bridge Route API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

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

The publisher's own server: Agent.chain.tokyo Address Contracts

VerifiedSSEWeb executableWeb Search & ScrapingFinance

Overview

AI-generated overview

Remote MCP endpoint that returns ranked cross-chain bridge routes with fees, timing and providers, paid per call in USDC via x402.

What you can do
Find ranked cross-chain bridge routes between chains and tokens, with provider, estimated time, fee in USD, expected amount received and step-by-step route details (approve, bridge, swap). Same lookup available as a GET or POST variant. Routes are sourced from LI.FI across many chains and bridges.
When to use it
Useful when an assistant needs to compare the cheapest or fastest way to move tokens between blockchains, for example for multi-chain portfolio planning. Not intended for gas price lookups.
Requirements
A remote MCP endpoint reached over SSE; no local package, signup or API key. Each call is paid per request in USDC on Base L2 through the x402 protocol, so an x402-capable client with a funded wallet is needed to complete the payment challenge.
Before you install
Every call costs money ($0.008 per route lookup) and is settled in USDC on Base, so a wallet must be funded and spending should be bounded. Payment details go through third-party facilitators (Coinbase CDP, PayAI). The server only returns route information; it does not execute bridges, but the returned steps should be reviewed before acting on them.

Installation

In SourceWeft

  1. Open Cross-Chain Bridge Route API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fbridge-routes/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "cross-chain-bridge-route-api": {
      "type": "sse",
      "url": "https://bridge-routes.api.klymax402.com/mcp"
    }
  }
}

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.):

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

Quickstart -- HTTP (x402)

bash
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:

json
{"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:

json
{"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

Source: README.md at commit 27cd2e6

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Chain integrations

Agent.chain.tokyo Address Contracts

tokyo.chain.agentOfficial publisher

Lets an assistant rent a Japan mailing address for an agent: browse locations and floors, create a 55 USDC payment intent, and track contracts and events.

Streamable HTTPWeb executable
Business & Commerce9 toolsOct 30, 2026

DeviceChain

io.devicechain

Read-only MCP tools for a self-hosted DeviceChain IoT instance, letting an assistant inspect devices, telemetry and alarms.

Streamable HTTPWeb executable
Cloud & InfrastructureNot indexed yetNov 7, 2026

BridgePilot — cross-chain route quotes

Published by GitHub account ert1981

BridgePilot — cross-chain route quotes's hosted MCP server; no sign-in required; Streamable HTTP; 1 tool.

Streamable HTTPWeb executable
1 toolOct 30, 2026

BrainChain

com.usebrainchain

Lets an assistant hand a task brief to a frontier model hired and graded by an AI agent, paying in USDG or USDC only for work that passes the quality levels…

STDIODesktop only
AI & MLNot validated yetNov 7, 2026

Agent Data Tools: Chain data

Published by GitHub account Nutshell2000

Pay-per-call remote MCP server for live blockchain reads: wallet balances, gas, transactions, logs and NFTs on five EVM chains plus Bitcoin.

Streamable HTTPWeb executable
AI & ML200+ toolsNov 7, 2026