ValueRouter MCP Server

A Model Context Protocol (MCP) server that provides AI agents with comprehensive cross-chain USDC bridging capabilities through ValueRouter. This server enables AI agents to seamlessly bridge USDC across multiple blockchain networks including Ethereum, Solana, Sui, and Cosmos ecosystem chains.

Features

• Multi-Chain Support: Bridge USDC across 15+ blockchain networks

• Real-Time Quotes: Get accurate bridging quotes with fees and timing estimates

• Transaction Simulation: Prepare bridge transactions without execution

• Status Tracking: Monitor bridge transaction progress in real-time

• Balance Queries: Check user token balances across all supported chains

• Fee Estimation: Calculate bridge fees and gas costs

Related MCP server: AMOCA Solana MCP Server

Supported Chains

Mainnet

• Ethereum (Chain ID: 1)

• Arbitrum One (Chain ID: 42161)

• Optimism (Chain ID: 10)

• Polygon (Chain ID: 137)

• Avalanche C-Chain (Chain ID: 43114)

• Base (Chain ID: 8453)

• Solana (Chain ID: 'solana')

• Sui (Chain ID: 'sui')

• Noble (Chain ID: 'noble-1')

• Osmosis (Chain ID: 'osmosis-1')

• Evmos (Chain ID: 'evmos_9001-2')

• Sei (Chain ID: 'pacific-1')

• Coreum (Chain ID: 'coreum-mainnet-1')

• dYdX (Chain ID: 'dydx-mainnet-1')

Testnet

• Goerli (Chain ID: 5)

• Sepolia (Chain ID: 11155111)

• Solana Devnet (Chain ID: 'solana-devnet')

• Sui Testnet (Chain ID: 'sui-testnet')

• Noble Testnet (Chain ID: 'grand-1')

• Avalanche Fuji (Chain ID: 43113)

• Arbitrum Goerli (Chain ID: 421613)

• Optimism Goerli (Chain ID: 420)

• Polygon Mumbai (Chain ID: 80001)

Installation

Usage

Starting the Server

Environment Variables

Create a .env file in your project root:

Available Tools

1. get_supported_chains

Get all supported chains for USDC bridging.

Parameters:

• includeTestnets (boolean, optional): Include testnet chains (default: false)

Example:

Response:

2. get_supported_tokens

Get supported tokens for bridging.

Parameters:

• chainId (number|string, optional): Specific chain ID to get tokens for

• includeTestnets (boolean, optional): Include testnet tokens (default: false)

Example:

3. get_bridge_quote

Get a quote for bridging USDC between chains.

Parameters:

• fromChainId (number|string): Source chain ID

• toChainId (number|string): Destination chain ID

• fromToken (object): Source token details

• toToken (object): Destination token details

• amount (string): Amount to bridge in smallest unit (wei, lamports, etc.)

• slippageBps (number, optional): Slippage tolerance in basis points (default: 100)

• userAddress (string, optional): User address for better quote accuracy

Example:

Response:

4. execute_bridge

Execute a bridge transaction (simulation only).

Parameters:

• fromChainId (number|string): Source chain ID

• toChainId (number|string): Destination chain ID

• fromToken (object): Source token details

• toToken (object): Destination token details

• amount (string): Amount to bridge

• recipientAddress (string): Recipient address on destination chain

• userAddress (string): User address initiating the transaction

• slippageBps (number, optional): Slippage tolerance in basis points

• memo (string, optional): Memo for Cosmos chains

Example:

Response:

5. get_transaction_status

Get the status of a bridge transaction.

Parameters:

• transactionHash (string): Transaction hash to check status for

• fromChainId (number|string): Source chain ID

• toChainId (number|string): Destination chain ID

Example:

Response:

6. get_user_balance

Get user token balance on a specific chain.

Parameters:

• chainId (number|string): Chain ID to check balance on

• tokenAddress (string): Token contract address

• userAddress (string): User address to check balance for

Example:

Response:

7. estimate_bridge_fees

Estimate fees for a bridge transaction.

Parameters:

• fromChainId (number|string): Source chain ID

• toChainId (number|string): Destination chain ID

• amount (string): Amount to bridge

• tokenAddress (string, optional): Token address (defaults to USDC)

Example:

Response:

Error Handling

All tools return structured error responses when something goes wrong:

Common error codes:

• UNSUPPORTED_CHAIN: Chain is not supported

• INVALID_TOKEN: Token address is invalid

• INSUFFICIENT_BALANCE: User has insufficient balance

• QUOTE_ERROR: Failed to get quote

• BRIDGE_ERROR: Failed to prepare bridge transaction

• STATUS_ERROR: Failed to get transaction status

• BALANCE_ERROR: Failed to get balance

Chain-Specific Notes

Ethereum & EVM Chains

• Use 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE for native ETH

• Gas fees are in wei (18 decimals)

• Bridge fees are 0.05% (5 basis points)

Solana

• Use So11111111111111111111111111111111111111112 for native SOL

• Gas fees are in lamports (9 decimals)

• Requires WSOL wrapping for bridging

Sui

• Use 0x2::sui::SUI for native SUI

• Gas fees are in MIST (9 decimals)

• Supports Move-based tokens

Cosmos Chains

• Use denomination strings like uusdc, uosmo, etc.

• Gas fees vary by chain

• Supports IBC transfers

Integration Examples

Basic Bridge Flow

Security Considerations

• Simulation Only: The execute_bridge tool only simulates transactions and returns transaction data. It does not execute real transactions.

• Address Validation: All addresses are validated before processing

• Amount Validation: Amounts are validated to prevent overflow errors

• RPC Security: Use secure RPC endpoints and API keys

• Rate Limiting: Implement rate limiting for production use

Development

Building

Testing

Linting

Contributing

1. Fork the repository

2. Create a feature branch

3. Make your changes

4. Add tests

5. Submit a pull request

License

MIT License - see LICENSE file for details

Support

For support and questions:

• GitHub Issues: ValueRouter MCP Server Issues

• Discord: ValueRouter Community

• Documentation: ValueRouter Docs

Changelog

See CHANGELOG.md for release history.