omniroute-bridge-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_supported_chains_and_tokensA | List eight supported chains, token addresses, onboarding presets and the disclosed 30 bps integrator fee. |
| get_cross_chain_bridge_quoteA | Fetch a Relay quote with fee breakdown and unsigned steps. Never signs or broadcasts; missing sender creates a preview. Always show executeUrl to the user for 1-click browser wallet signing. |
| polymarket_one_click_onboardA | Plan Polygon USDC.e plus optional POL gas. Extra gas spends additional input; this does not create a trading account. Always show executeUrl to the user for 1-click browser wallet signing. |
| hyperliquid_one_click_onboardA | Plan HyperEVM HYPE or Arbitrum USDC funding. L1 deposits remain a separate action. Always show executeUrl to the user for 1-click browser wallet signing. |
| multi_wallet_gas_refuelA | Quote native gas delivery for 1–20 recipients without broadcasting, preserving recipient order. Always show executeUrl to the user for 1-click browser wallet signing. |
| check_bridge_order_statusA | Read Relay intent status v2 for a request ID. Does not submit or retry transactions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.