Skip to main content
Glama
Sign In
omniroute-bridge-mcp

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

      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
      87 npm
      31
      MIT
    • @quackai/q402-mcp

      @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
      392 npm
      1
      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
      78 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.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct action: discovery (list_supported_chains_and_tokens), quoting (get_cross_chain_bridge_quote), protocol-specific onboarding (polymarket, hyperliquid), gas refueling, and status polling. The two onboarding tools are near-identical in shape but clearly separated by protocol name, and the descriptions differentiate the onboarding plans from the generic bridge quote.

    Naming Consistency3/5

    Half the tools follow a clean verb_noun pattern (list_supported_chains_and_tokens, get_cross_chain_bridge_quote, check_bridge_order_status), but the onboarding tools use entity-first ordering (polymarket_one_click_onboard) and multi_wallet_gas_refuel has no leading verb. The mixed conventions are still readable but break the pattern.

    Tool Count5/5

    Six tools is a tight, well-scoped surface for a bridge/onboarding workflow: discovery, quoting, two protocol-specific onboarding paths, refuel, and status. No tool feels redundant or padded.

    Completeness4/5

    The surface covers the full read-only lifecycle: list supported assets, get quotes/plans, and poll order status, with signing explicitly handed off via executeUrl. Minor gaps exist (e.g. no fee-only or supported-recipient lookup separate from the list tool), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources