Alchemy MCP Server

com.alchemyPublished by alchemy.comOfficial publisherv0.9.5Updated Oct 29, 2026

Blockchain data across 100+ chains: token prices, NFTs, transfers, simulation, traces, Solana DAS

VerifiedStreamable HTTPWeb executableDatabases Finance

Server details

Identifier: com.alchemy/mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to alchemy.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.alchemy%2Fmcp.svg)](https://sourceweft.com/mcp/com.alchemy%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted Alchemy MCP server that gives AI assistants access to blockchain APIs and onchain data across 100+ chains, including token prices, NFTs, transfers and…

What you can do: Query blockchain data across 100+ chains through Alchemy's hosted APIs
Look up token prices, NFTs and transfers
Simulate transactions and inspect traces
Access Solana DAS data
Connect over Streamable HTTP with no local install
When to use it: Useful when an assistant needs onchain data or transaction simulation for blockchain work, such as checking token prices, NFT holdings, transfers or traces across multiple chains, without building your own API integration.
Requirements: A remote MCP endpoint at mcp.alchemy.com using Streamable HTTP transport. Authentication is OAuth: you sign in with an Alchemy account when prompted. No API key or local install is required.

Before you install

Signing in grants the server access through your Alchemy account, so review the OAuth consent and account permissions. Queries and account data go to Alchemy as a third party. The retired local npm package and its ALCHEMY_API_KEY setup should be replaced with the hosted endpoint.

Installation

In SourceWeft

Open Alchemy MCP Server in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.alchemy%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "alchemy": {
      "type": "http",
      "url": "https://mcp.alchemy.com/mcp"
    }
  }
}

README

Alchemy MCP Server

[!IMPORTANT] The legacy local MCP server has been retired. Its source code has been removed from this repository, and the @alchemy/mcp-server npm package will stop working on September 30, 2026. Use the hosted Alchemy MCP Server at https://mcp.alchemy.com/mcp instead.

The hosted Alchemy MCP Server gives AI agents access to Alchemy's blockchain APIs and onchain data. It authenticates via OAuth — just sign in with your Alchemy account when prompted. No API key or local install required.

Full documentation: alchemy.com/docs/alchemy-mcp-server

Setup

Client	Setup
Claude Code	`claude mcp add alchemy --transport http https://mcp.alchemy.com/mcp`
Codex	`codex mcp add alchemy --url https://mcp.alchemy.com/mcp`
Cursor	Add to `~/.cursor/mcp.json` or `.cursor/mcp.json` — see JSON config below
Windsurf	Add to `~/.codeium/windsurf/mcp_config.json` — see JSON config below
VS Code Copilot	Add to `.vscode/mcp.json` — see JSON config below
Claude Desktop	Add to `claude_desktop_config.json` — see JSON config below
Cline	Open `Cline: MCP Servers` from the VS Code command palette — see JSON config below

JSON config for Cursor / Windsurf / Claude Desktop / Cline

json

{  "mcpServers": {    "alchemy": {      "type": "streamable-http",      "url": "https://mcp.alchemy.com/mcp"    }  }}

{  "mcpServers": {    "alchemy": {      "type": "streamable-http",      "url": "https://mcp.alchemy.com/mcp"    }  }}

JSON config for VS Code Copilot

json

{  "servers": {    "alchemy": {      "type": "http",      "url": "https://mcp.alchemy.com/mcp"    }  }}

{  "servers": {    "alchemy": {      "type": "http",      "url": "https://mcp.alchemy.com/mcp"    }  }}

For any other MCP-compatible client, point it at https://mcp.alchemy.com/mcp using Streamable HTTP transport.

Migrating from the local server

If your MCP config runs the local server through npx, like this:

json

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

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

replace that entry with the hosted server config for your client from the Setup section above. You can drop ALCHEMY_API_KEY from your MCP config; the hosted server signs you in with your Alchemy account instead.

Source: README.md at commit fb4ceab

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v0.9.5LatestOct 29, 2026
v0.9.3Oct 21, 2026
v0.9.1Oct 19, 2026
v0.8.2Oct 16, 2026
v0.8.0Oct 14, 2026
v0.7.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Other Alchemy integrations

Alchemy Eth

Published by GitHub account pipeworx-io

Pipeworx gateway pack exposing Alchemy Ethereum and L2 RPC, token, NFT and transfer tools, plus a router that reaches a much larger data catalog.

Streamable HTTPWeb executable

Web Search & Scraping53 toolsOct 30, 2026

Alchemy

Published by GitHub account fernforge

Serves a writing ruleset that steers an AI assistant away from common LLM prose tics when it drafts documentation, commits, or other text.

STDIODesktop only

Knowledge & MemoryNot validated yetOct 24, 2026

Alchemy Nft

com.mcparmory

A local MCP server that lets an assistant retrieve NFT metadata, ownership and contract details across blockchains via the Alchemy NFT API.

STDIODesktop only

DatabasesNot validated yetOct 24, 2026