Alchemy MCP Plugin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALCHEMY_API_KEY | Yes | Your API key from Alchemy (https://www.alchemy.com/) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_nfts_for_ownerC | Get NFTs owned by a specific wallet address |
| get_nft_metadataC | Get metadata for a specific NFT |
| get_nft_salesC | Get NFT sales data for a contract or specific NFT |
| get_contracts_for_ownerC | Get NFT contracts owned by an address |
| get_floor_priceC | Get floor price for an NFT collection |
| get_owners_for_nftC | Get owners of a specific NFT |
| get_nfts_for_contractC | Get all NFTs for a contract |
| get_transfers_for_contractC | Get transfers for an NFT contract |
| get_transfers_for_ownerC | Get NFT transfers for an owner |
| get_token_balancesC | Get token balances for a specific address |
| get_token_metadataC | Get metadata for a token contract |
| get_tokens_for_ownerC | Get tokens owned by an address |
| get_asset_transfersC | Get asset transfers for a specific address or contract |
| get_transaction_receiptsC | Get transaction receipts for a block |
| get_block_numberB | Get the latest block number |
| get_block_with_transactionsC | Get a block with its transactions |
| get_transactionC | Get transaction details by hash |
| resolve_ensB | Resolve an ENS name to an address |
| lookup_addressB | Lookup the ENS name for an address |
| estimate_gas_priceC | Estimate current gas price |
| subscribeC | Subscribe to blockchain events |
| unsubscribeC | Unsubscribe from blockchain events |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Most tools have distinct purposes, but there is some overlap between get_nfts_for_owner and get_contracts_for_owner, as well as between get_asset_transfers, get_transfers_for_contract, and get_transfers_for_owner, which could cause minor confusion. However, descriptions help clarify the specific focus of each tool.
All tool names follow a consistent verb_noun pattern with underscores, such as get_block_number, estimate_gas_price, and lookup_address. There are no deviations in naming conventions, making the set highly predictable and readable.
With 22 tools, the count is on the higher side for a blockchain-focused server, bordering on heavy but still manageable. It covers multiple aspects like NFTs, tokens, transactions, and events, but may feel slightly bloated compared to more streamlined sets.
The tool set provides comprehensive coverage for blockchain interactions, including data retrieval (blocks, transactions, NFTs, tokens), metadata access, transfers, ownership queries, and event subscriptions. There are no obvious gaps, and it supports full lifecycle operations for the domain.