Connections & Capabilities
Connects To
Capabilities
Quickstart
Config
{
"mcpServers": {
"alchemy": {
"command": "npx",
"args": [
"-y",
"@alchemy/mcp-server"
],
"env": {
"ALCHEMY_API_KEY": "YOUR_API_KEY"
}
}
}
}Exposed MCP Tools (11)
fetchTokenPriceBySymbolRetrieves the current price of a token by its symbol.
Read-only operation, no side effects.
fetchTokenPriceByAddressRetrieves the current price of a token by its contract address.
Read-only operation, no side effects.
fetchTokenPriceHistoryBySymbolRetrieves historical price data for a token by its symbol.
Read-only operation, no side effects.
fetchTokenPriceHistoryByTimeFrameRetrieves historical price data for a token within a specified timeframe.
Read-only operation, no side effects.
fetchTokensOwnedByMultichainAddressesRetrieves token balances for addresses across multiple blockchain networks.
Read-only operation, no side effects.
fetchAddressTransactionHistoryRetrieves transaction history for addresses across multiple blockchain networks.
Read-only operation, no side effects.
fetchTransfersRetrieves detailed asset transfer data with filtering options.
Read-only operation, no side effects.
fetchNftsOwnedByMultichainAddressesRetrieves NFTs owned by addresses, including spam filtering.
Read-only operation, no side effects.
fetchNftContractDataByMultichainAddressRetrieves NFT contract data for addresses.
Read-only operation, no side effects.
sendTransactionSends transactions via Smart Contract Accounts using a configured wallet agent server.
Requires a configured wallet agent server and can result in financial loss if used incorrectly.
swapExecutes token swaps via DEX protocols (Uniswap) using a configured wallet agent server.
Requires a configured wallet agent server and carries the risk of slippage and impermanent loss.
Safety Assessment
The Alchemy MCP server offers safe read-only access to blockchain data. However, transaction and swap functionalities introduce risks related to wallet security and smart contract interactions. Proper configuration and monitoring of the wallet agent server are crucial.
- Read-only methods for querying blockchain data.
- Requires API key for authentication.
- Clear separation of read and write methods.
- Wallet agent server required for transaction signing.
- Potential for unauthorized transactions if wallet agent server is compromised.
- Reliance on external wallet infrastructure introduces dependencies.
- Improper API key management could lead to unauthorized access.
- Smart contract interactions carry inherent risks.
