Skip to main content
Glama
c-viper-work

omniroute-bridge-mcp

Official
by c-viper-work
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to omniroute-bridge-mcp

No user-submitted related servers found.

    Related Servers

    • deBridge by debridge-finance

      deBridgeofficial

      debridge-finance
      A
      license
      A
      quality
      D
      maintenance
      deBridge MCP finds optimal cross-chain swap routes, check fees and conditions, and initiate non-custodial trades across major blockchain networks. Supported: Ethereum, Solana, Arbitrum, Base, BNB Chain, Polygon, Optimism, Avalanche, Linea, Berachain, Tron, Cronos, Gnosis, Monad, Sonic, Flow, HyperEVM, Sei, Story, Injective, Abstract, MegaETH, Mantle, Plasma, Zilliqa, Sophon, Bob, Neon, and more
      5
      72 npm
      31
      MIT
    • @quackai/q402-mcp by quackai-org

      @quackai/q402-mcpofficial

      quackai-org
      A
      license
      A
      quality
      C
      maintenance
      MCP server for gasless USDC, USDT, RLUSD, and USDG payments across 12 EVM chains via EIP-7702, enabling quote, route, and settle stablecoin payments from any MCP client.
      50
      177 npm
      Apache 2.0

    • web3agent

      Apegurus
      A
      license
      C
      quality
      C
      maintenance
      Web3 MCP proxy server for AI agents: EVM execution, DeFi swaps, bridges, advanced orders, market data, wallet management, and confirmation-gated writes.
      100
      37 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct primary action: listing chains, quoting a bridge, onboarding to two named venues, refueling gas, and checking status. The only mild overlap is between the generic bridge quote and the venue-specific onboarding plans, but descriptions clarify their boundaries.

    Naming Consistency3/5

    All names use snake_case, which is consistent. However, three tools start with a verb (list_, get_, check_) while three start with a domain or resource prefix (polymarket_, hyperliquid_, multi_wallet_), creating a mixed naming convention.

    Tool Count5/5

    Six tools is a well-scoped set for a cross-chain bridge and onboarding planning server. Each tool has a clear, non-redundant role and none feels extraneous.

    Completeness4/5

    The surface covers listing supported assets, quoting bridges, planning onboarding for two venues, refueling gas, and checking bridge order status. Minor gaps exist, such as status tracking for non-bridge onboarding or gas refuel operations, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources