Relay Protocol MCP Server
Provides tools for cross-chain bridging, token swapping, and real-time price discovery on the Ethereum network.
Enables cross-chain bridging, multi-chain token swaps, and real-time price monitoring for the Optimism blockchain network.
Facilitates cross-chain bridging and token swaps on the Polygon network, including price discovery and transaction status tracking.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Relay Protocol MCP Server Get a quote to bridge 100 USDC from Ethereum to Polygon"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Relay Protocol MCP Server
The first community-built MCP server for Relay Protocol.
Status: discontinued
Relay Protocol is still active. This community project is retired because its API access is changing, and Relay's team now provides its own MCP server.
Read Relay's Requests v3 migration guide.
This server no longer fetches Relay data. It only returns a retirement notice; the original source remains here for reference.
Related MCP server: Universal Crypto MCP
License
MIT. See LICENSE.
Available Tools
9 toolsrelay_get_chainsA
Get all supported chains for cross-chain operations. Returns detailed information about each chain including RPC URLs, explorers, currencies, and supported tokens.
Common Chain IDs: • Ethereum: 1 • Optimism: 10 • Polygon: 137 • Arbitrum: 42161 • Base: 8453 • BNB Chain: 56
Optional: Use includeChains parameter to filter specific chains (comma-separated chain IDs).
Inputs: includeChains.
relay_get_currenciesA
Get currencies metadata from a curated list. Supports filtering by chain IDs, search terms, addresses, and other criteria.
Common Examples: • Find USDC on specific chains: {"chainIds": [1, 10, 8453], "term": "usdc", "verified": true, "limit": 10} • All major tokens on Ethereum: {"chainIds": [1], "defaultList": true, "limit": 20} • Search by contract address: {"address": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48", "includeAllChains": true} • Verified tokens only: {"verified": true, "limit": 50} • Deposit-address supported tokens: {"depositAddressOnly": true}
Tip: Use verified=true to avoid scam/fake tokens. Use term to search by symbol/name.
Inputs: defaultList, chainIds, term, address, +7 more.
relay_get_execution_statusA
Get the current execution status of a cross-chain request. Returns status, transaction hash, and other execution details.
When to use: After executing a quote/swap, use the requestId from the response to monitor progress. Request ID format: Hex string starting with "0x" (e.g., "0x1234abcd...") Status values: "pending", "success", "failed", "insufficient-balance"
Example workflow: relay_get_quote → get requestId → relay_get_execution_status
Inputs: requestId (required).
relay_get_quoteA
Get an executable quote for bridging tokens between chains or swapping within a chain. Always use TOKEN CONTRACT ADDRESSES, not symbols. Use relay_get_currencies to find token addresses.
Common Examples: • Bridge USDC Ethereum→Optimism: user="0x123...", originChainId=1, destinationChainId=10, originCurrency="0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48", destinationCurrency="0x0b2c639c533813f4aa9d7837caf62653d097ff85", amount="1000000", tradeType="EXACT_INPUT" • Bridge USDC Ethereum→Base: originChainId=1, destinationChainId=8453, destinationCurrency="0x833589fcd6edb6e08f4c7c32d4f71b54bda02913" • Same-chain swap on Ethereum: originChainId=1, destinationChainId=1, different token addresses
Token Format: Always use contract addresses (checksummed preferred) Amount Format: Smallest unit - "1000000"=1 USDC, "1000000000000000000"=1 ETH
Inputs: user (required), originChainId (required), destinationChainId (required), originCurrency (required), +4 more.
relay_get_requestsA
Get all cross-chain transactions with advanced filtering and pagination.
Use Cases: • List all transactions for a specific user • Find transactions by hash, chain IDs, or time range • Monitor transaction history with pagination • Filter by request status and referrer
Pagination: Use limit (max 50) and continuation token for large result sets. Sorting: Sort by createdAt or updatedAt in asc/desc order.
Inputs: limit, continuation, user, hash, +12 more.
relay_get_token_priceA
Get the current price of a token on a specific chain. Requires the token contract address, not symbol. Use relay_get_currencies to find token addresses.
Examples: • USDC on Ethereum: chainId=1, address="0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48" • WETH on Optimism: chainId=10, address="0x4200000000000000000000000000000000000006" • USDC on Base: chainId=8453, address="0x833589fcd6edb6e08f4c7c32d4f71b54bda02913"
Inputs: chainId (required), address (required).
relay_swap_multi_inputA
Execute multi-chain token swaps. IMPORTANT: For EXACT_INPUT, do NOT include "amount" at root level - only in origins array. For EXACT_OUTPUT, include "amount" at root level. Always use TOKEN CONTRACT ADDRESSES. Examples:
EXACT_INPUT (Bridge 1 USDC from Ethereum to Optimism): {"user": "0x123...", "origins": [{"chainId": 1, "currency": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48", "amount": "1000000"}], "destinationChainId": 10, "destinationCurrency": "0x0b2c639c533813f4aa9d7837caf62653d097ff85", "tradeType": "EXACT_INPUT"}
EXACT_OUTPUT (Get exactly 100 USDC on Base): {"user": "0x123...", "amount": "100000000", "origins": [{"chainId": 1, "currency": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48", "amount": "50000000"}], "destinationChainId": 8453, "destinationCurrency": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "tradeType": "EXACT_OUTPUT"}
Inputs: user (required), origins (required), destinationCurrency (required), destinationChainId (required), +9 more.
relay_transactions_indexA
Notify the Relay backend about a transaction. This is used to index and track transactions for cross-chain operations.
When to use: • After executing a transaction from a quote response • When you want Relay to track a specific transaction • For proper status monitoring and request linking
Example: After sending the deposit transaction from relay_get_quote response, call this tool with the transaction hash and chain ID to enable proper tracking.
Required: txHash (0x...), chainId (number) Optional: requestId (from quote response for linking)
Inputs: txHash (required), chainId (required), requestId.
relay_transactions_singleA
Notify the Relay backend to index transfers, wraps and unwraps for a specific transaction.
When to use: • Index specific transfers within a transaction • Track wrap/unwrap operations • Associate transaction data with a request ID
Difference from relay_transactions_index: • This is for indexing specific transfers/wraps/unwraps • relay_transactions_index is for general transaction tracking
Required: requestId, chainId (string), tx (transaction hash)
Inputs: requestId (required), chainId (required), tx (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Tools are mostly distinct with clear purposes. Slight overlap between get_execution_status and get_requests (both provide status info) and between transactions_index and transactions_single, but descriptions help differentiate.
Naming follows a consistent 'relay_' prefix, but verbs are mixed: 'get_' tools are verb_noun, while 'swap_multi_input' and 'transactions_index'/'transactions_single' deviate from that pattern, causing inconsistency.
9 tools is appropriate for the cross-chain swap domain. Each tool covers a distinct step in the workflow without being excessive or insufficient.
Core workflows (discover chains/tokens, get quotes, execute swaps, monitor status) are well-covered. Minor gaps like token approval management are absent but not critical for basic operations.
Maintenance
Related MCP Connectors
Quote, create and track crypto swaps across hundreds of coins and networks. No account needed.
Best-price cross-chain swap quotes across 70 chains, EVM and Solana. Holds no keys, never signs.
Token swaps at the best net price on 9 EVM chains and Solana. No API key, non-custodial.
Swap, bridge and get gas on 6 EVM chains. Each plan states its outcome before you sign. No API key.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables cross-chain cryptocurrency swap quotes and operations using the deBridge DLN protocol. Provides read-only access to swap estimates, supported chains, token information, and order status tracking across multiple blockchain networks.1-
- FlicenseCqualityBmaintenanceEnables AI agents to interact with any EVM-compatible blockchain through natural language, supporting token swaps, cross-chain bridges, staking, lending, governance, gas optimization, and portfolio tracking across networks like Ethereum, BSC, Polygon, Arbitrum, and more.10041 npm44-
- AlicenseAqualityCmaintenanceProvides cross-chain bridge and swap tools for AI agents using the Relay Protocol to interact with multiple blockchain networks. It enables agents to query supported chains, obtain transaction quotes, and generate unsigned transaction data for token transfers and swaps.105MIT

Flashift MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to compare rates across 100+ blockchains and 15+ liquidity providers, create non-custodial cross-chain swaps, and track transaction status without any API key. It exposes tools for listing currencies, quoting swaps with AI-ranked routing tags, generating deposit addresses, and monitoring exchanges to completion.MIT