F
licenseA
qualityD
maintenanceA Model Context Protocol server that enables AI agents to autonomously execute cross-chain trading operations on Paloma DEX across seven EVM chains including Ethereum, Arbitrum, and Polygon.
21
-
ValueRouter MCP Server
Related Servers
Alternatives to ValueRouter MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI agents to interact with 30+ Ethereum-compatible blockchain networks, providing services like token transfers, contract interactions, and ENS resolution through a unified interface.2864378MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server enabling AI agents to interact with the Solana blockchain for DeFi operations like checking balances, transferring tokens, executing swaps, and fetching price data.1222MIT
- FlicenseAqualityCmaintenanceMCP server that lets AI agents bridge native USDC between networks (Ethereum, Base, Arbitrum, OP Mainnet, Polygon, Avalanche, and testnets) via Circle CCTP V2, featuring idempotent transfers, disk-persisted state, balance/gas checks, and configurable limits.6-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models to interact with the Solana blockchain, providing RPC methods, wallet management, DeFi trading capabilities, and Helius API integration for enhanced Solana development.5MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server enabling AI assistants to create, buy, and sell tokens on the Pump.fun platform on Solana.622-
TDQS
B3.4/5.0
Scored across 7 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no ambiguity: fee estimation, transaction execution, quote retrieval, chain/token support queries, status checking, and balance fetching. The descriptions clearly differentiate between informational queries (get_*) and action-oriented tools (estimate_*, execute_*), making misselection unlikely.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with clear, descriptive names. The naming convention is uniform throughout: estimate_bridge_fees, execute_bridge, get_bridge_quote, get_supported_chains, get_supported_tokens, get_transaction_status, get_user_balance. No mixing of styles or inconsistent verb usage is present.
Tool Count5/5
With 7 tools, this server is well-scoped for its bridge transaction domain. Each tool earns its place by covering distinct aspects of the bridging workflow: preparation (estimate, quote), execution (execute), information (chains, tokens, status, balance). The count is neither too thin nor bloated, fitting typical MCP server expectations.
Completeness4/5
The tool surface provides excellent coverage for core bridge transaction workflows: quote→estimate→execute→status, plus supporting queries for chains, tokens, and balances. The only minor gap is the lack of a tool for canceling or modifying transactions, but agents can work around this given the simulation-only nature of execute_bridge. Overall, it's nearly complete for the stated purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues