Server facts
alchemy-mcp-server
Project
- Author
- alchemyplatform
- License
- MIT
- Category
- Blockchain & Web3
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 88
- Last commit
- Data as of
Overview
Token research and wallet inspection sit alongside contract debugging in Alchemy's MCP integration. Agents can retrieve current prices by ticker or contract address, request historical prices for date ranges or natural-language periods, and inspect balances and transfers across networks. NFT tools cover ownership, metadata, sales, floor prices, rarity, and spam checks. For deeper investigation, the tool set includes transaction traces and simulations of execution or asset changes, plus Ethereum Beacon Chain validator data and Solana asset searches.
Transaction submission and swaps use Smart Contract Accounts and depend on a separately configured wallet agent server for signing and broadcasting. The local Node.js implementation communicates over STDIO and requires an Alchemy API key for blockchain queries. Released under the MIT license, this repository remains available for local development, reference, and migration; it is not actively maintained, and Alchemy plans to retire it. The README directs new users to the maintained hosted alternative, which uses OAuth with an Alchemy account rather than an API key or local installation. It also warns that local tool coverage and behavior may lag behind the hosted service.
alchemy-mcp-server setup notes
- alchemy-mcp-server records stdio only; confirm a network transport upstream before planning remote access.