Alchemy MCP Server
OfficialRelated Servers
Alternatives to Alchemy MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceThe first blockchain & cryptocurrency MCP server that connects AI agents to Ethereum, Solana, Bitcoin, and cryptocurrency markets.915 npmMIT
- FlicenseAqualityCmaintenanceAn MCP server that equips AI assistants with curated knowledge and live chain data for the Alkanes metaprotocol and Subfrost network, enabling them to read docs, query the chain, and scaffold contracts.213-
- AlicenseCqualityBmaintenanceA comprehensive MCP server for tooling interactions(40+) and resource accessibility(60+) with Algorand blockchain, plus many useful prompts.10013 npm44MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes blockchain data as native tools for AI agents, enabling read-only queries like wallet balances and token holdings on Ethereum, Polygon, and Base.MIT
- AlicenseAqualityDmaintenanceMCP server that enables AI agents to build and deploy Ethereum applications using Scaffold-ETH.348 npm2MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that lets any AI agent operate a wallet directly on-chain: create wallets, send, swap, bridge, and deploy contracts across EVM and Bitcoin networks.1MIT
TDQS
Scored across 97 tools
Descriptive names with clear qualifiers (e.g., debugTraceBlockByHash vs debugTraceBlockByNumber, getBeaconStateValidatorBalances vs getBeaconStateValidatorById) allow agents to distinguish tools. Some overlap exists between getNFTsForCollection and getNFTsForContract, but descriptions clarify the distinction. Overall, 97 tools are well-segmented by domain.
Naming conventions are mixed: most use camelCase, but verbs vary (get, fetch, debug, trace, simulate, compute, etc.) with no uniform pattern. Within domains (e.g., Beacon, Solana, debug), consistency is high, but across the server the style is inconsistent, occasionally using 'list' instead of 'get' (listSupportedNetworks).
With 97 tools, the server is over-scoped, covering Ethereum, Beacon Chain, Solana, NFTs, ERC-4337, debugging, and more. While each domain has its tools, the sheer number creates cognitive load and many are highly specialized or redundant (e.g., multiple trace variants). Consolidating some tools or splitting into multiple servers would improve coherence.
The tool surface is remarkably comprehensive, covering data retrieval, transaction simulation, NFT metadata, token prices, Beacon Chain operations, Solana assets, and debugging. It includes both querying and some state-changing operations (sendTransaction, swap). No obvious gaps for a blockchain data provider.