Verified

Alchemy MCP Server

Blockchain APIs from Alchemy via an open-source TypeScript implementation.

Data last scanned today · Reviewed today

25 2 dangerous tools11 tools★ 88TypeScriptMIT

Overview

The Alchemy MCP Server allows users to interface with blockchain data directly through an MCP-compliant architecture. Originally designed to run as a local STDIO server, this TypeScript project provides a bridge between AI models and Alchemy's infrastructure.

Our verdict

This repository carries a high-risk score of 40/100 and is not recommended for use. The maintainers have explicitly labeled this version as legacy and state it is not actively maintained, with plans to sunset the repository entirely. Since the authentication methods and read-only status have not been editorially reviewed, users should transition to the official hosted Alchemy MCP server.

Published under the MIT open-source license
Small footprint with only six direct dependencies
Maintains a bus-factor of seven active contributors

Deprecated legacy status with no active maintenance
Security mechanisms remain unverified by editorial review
Missing formal documentation for authentication methods

Setup

Claude Desktop

{
  "mcpServers": {
    "alchemy-mcp-server": {
      "args": [
        "-y",
        "@alchemy/mcp-server"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
fetchTokenPriceBySymbol	Gets current price data for tokens by symbol	low
fetchTokenPriceByAddress	Gets current price data for tokens by contract address	low
fetchTokenPriceHistoryBySymbol	Gets historical price data for tokens with specific date ranges	low
fetchTokenPriceHistoryByTimeFrame	Gets historical price data using flexible time frames or natural language	low
fetchTokensOwnedByMultichainAddresses	Gets token balances for addresses across multiple networks	low
fetchAddressTransactionHistory	Gets transaction history for addresses across multiple networks	low
fetchTransfers	Gets detailed asset transfer data with advanced filtering options	low
fetchNftsOwnedByMultichainAddresses	Gets all NFTs owned by addresses with spam filtering	low
fetchNftContractDataByMultichainAddress	Gets NFT contract data for addresses	low
sendTransaction	Sends transactions via Smart Contract Accounts	high

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›Should I use the local STDIO server or the hosted version?

You should use the hosted Alchemy MCP Server at https://mcp.alchemy.com/mcp. The local STDIO server in this repository is legacy, not actively maintained, and is planned to be sunset.

›What authentication is required for the hosted MCP server?

The hosted server authenticates via OAuth. You simply sign in with your Alchemy account when prompted, and no local API key or installation is required.

›What is required to use the local STDIO version of the server?

You must provide an ALCHEMY_API_KEY environment variable. The server is configured via your client's MCP configuration file using npx.

›Do all features work in the local STDIO server without additional setup?

No, the sendTransaction and swap methods require an additional AGENT_WALLET_SERVER environment variable. This server must be configured to handle the external wallet infrastructure for signing and broadcasting.