MCP servers · br0ski777

Cross-Chain Bridge Route API

MCP server that returns ranked cross-chain bridge routes with fees, estimated time and bridge providers, using LI.FI data and pay-per-call x402 payments.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

The server finds cross-chain bridge routes through LI.FI, covering more than 60 chains and 18 bridges. Its bridge_find_best_route tool takes a source chain, destination chain, token, amount in smallest units and an optional destination token. It returns routes ranked by value, each with the bridge provider, estimated completion time in seconds, total fee in USD, expected amount received, and step-by-step actions such as approval, bridging and swapping. Chain IDs are listed for Ethereum, Base, Arbitrum, Optimism, Polygon, BSC and Avalanche. A POST variant accepts the same parameters as a JSON body.

Use it when tokens need to move between blockchains and the cheapest or fastest bridge is needed for comparison. It does not return gas prices; the publisher points to gas_get_current_price for that.

It is added to an MCP client configuration. Each call is paid through x402 in USDC on Base L2, at $0.008 per call, with no API key or signup. An x402-aware client handles the payment cycle. The server is also reachable via ATXP and is part of the klymax402 marketplace of 100 micropayment APIs that share one wallet. The code is released under the MIT licence.

Limitations and requirements

Each call requires payment in USDC on Base L2 through an x402-aware client, so a funded wallet is needed. Each call is priced at $0.008.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    Cross-Chain Bridge Route API

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

    v1.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026