Universal Crypto MCP
Related Servers
Alternatives to Universal Crypto MCP
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityDmaintenanceEnables AI agents to perform blockchain operations like wallet management, token info, DeFi swaps, cross-chain bridging, and price checking across Ethereum, BNB Chain, and Solana.-- AlicenseCqualityDmaintenanceEnables AI agents to interact with cryptocurrency ecosystems through wallet management, trading operations (swaps, DCA, limit orders), staking, and multi-chain support starting with Solana.37GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform complex crypto operations like cross-chain routing, contract decoding, portfolio management, and anti-rug security checks, returning unsigned transactions for safe signing by the agent.MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive toolkit for building AI agents with blockchain capabilities, enabling interactions with multiple blockchain networks for tasks like wallet management, fund transfers, smart contract interactions, and cross-chain asset bridging.5GPL 3.0
- FlicenseBqualityDmaintenanceEnables AI assistants to discover, evaluate, and execute DeFi yield strategies across EVM and Solana chains through natural conversation, with transactions signed locally.159 npm1-
- FlicenseAqualityFmaintenanceDeFi execution and agent-to-agent economy tools for AI agents — swaps, yield, transfers, policy enforcement, trust scoring, A2A jobs, and P\&L across Ethereum, Base, Arbitrum, and Polygon.311-
TDQS
Scored across 720 tools
Massive functional overlap across hundreds of tools: multiple pairs do identical things (x402_pay_request/x402_pay_for_request, x402_balance/x402_check_balance, coingecko_simple_price/market_coingecko_simple_price, resolve_ens_name/reverse_resolve_address, etc.). Many similarly-named tools with unclear boundaries, and several whole families (indicator_* vs strategy_*) are semantically redundant. An agent would constantly misselect.
There are internally consistent sub-families (market_*, indicator_*, x402_*, geckoterminal_*, marketplace_*), but the overall convention is chaotic: chain prefixes mixed with domain prefixes and bare generic names (get_transaction, estimate_gas, create_wallet, execute_swap vs solana_get_balance, defi_get_protocols, server_health). Similar concepts use different verbs and ordering (get_coin_chart vs historical_prices vs market_coingecko_coin_market_chart).
720 tools is an extreme mismatch for any single MCP server, even for a 'universal' crypto surface. This volume makes discovery and selection impractical, and the breadth is achieved by bolting on many full provider SDKs rather than curating a focused toolset. It far exceeds even generous limits for a broad-scope server.
Some domains are over-covered (indicators, market data, x402/payments) while others are severely thin or incomplete: several chains only expose balance/history with no send (Bitcoin, Litecoin, Dogecoin), and many chain-specific APIs lack transaction submission, staking, or governance actions. The set is a patchwork of partially-integrated providers, leaving obvious lifecycle gaps for common crypto operations.