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. |
| polymarket_one_click_onboardC | Plan Polygon USDC.e plus optional POL gas. Extra gas spends additional input; this does not create a trading account. |
| hyperliquid_one_click_onboardA | Plan HyperEVM HYPE or Arbitrum USDC funding. L1 deposits remain a separate action. |
| multi_wallet_gas_refuelA | Quote native gas delivery for 1–20 recipients without broadcasting, preserving recipient order. |
| 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 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.
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.
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.
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.