Cross-Chain Bridge Route API

io.github.Br0ski777由 GitHub 帳號 Br0ski777 發布v1.1.0更新於 Oct 24, 2026

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

發布方自己的服務:Agent.chain.tokyo Address Contracts

已驗證SSE可網頁執行網頁搜尋與抓取金融

概覽

AI 產生的概覽

遠端 MCP 端點,回傳依費用、時間與提供者排序的跨鏈橋接路線,透過 x402 按次以 USDC 付費。

可以做什麼
查詢不同鏈與代幣之間的跨鏈橋接路線,回傳依最佳價值排序的結果,包含橋接協定、預估時間、美元費用、預期到帳數量與逐步路線(授權、橋接、兌換)。同一查詢提供 GET 與 POST 兩種呼叫方式。路線資料來自 LI.FI,涵蓋多條鏈與多個橋。
適用情境
適合需要比較在不同區塊鏈之間移轉代幣的最便宜或最快方式時使用,例如多鏈資產組合規劃。不適用於查詢 Gas 價格。
執行需求
透過 SSE 連線的遠端 MCP 端點,不需本機套件、註冊或 API 金鑰。每次呼叫按次以 Base L2 上的 USDC 付費,需使用支援 x402 且錢包有餘額的用戶端完成付款挑戰。
安裝前請注意
每次呼叫都會產生費用(每次路線查詢 0.008 美元),以 Base 上的 USDC 結算,需確保錢包有餘額並限制支出。付款資訊會經過第三方結算服務(Coinbase CDP、PayAI)。此伺服器只回傳路線資訊,不執行橋接,但回傳的步驟在執行前應人工確認。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Cross-Chain Bridge Route API,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 SSE。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.Br0ski777%2Fbridge-routes/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

來源:README.md,提交 27cd2e6

工具

0
SourceWeft 尚未讀取此伺服器的工具。

版本歷史

1
  1. v1.1.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式必需10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Chain 整合