What can @alchemy/mcp-server do?

blockchain rpc method invocation via mcp protocol, multi-chain network abstraction and routing, alchemy enhanced api exposure (token and nft data), mcp server lifecycle management and configuration, error handling and rpc failure recovery, schema-based tool parameter validation, transaction construction and signing preparation

@alchemy/mcp-server

MCP ServerFree

MCP server for using Alchemy APIs

Open Source

/ 100

7 capabilities

Capabilities7 decomposed

blockchain rpc method invocation via mcp protocol

Medium confidence

Exposes Alchemy's blockchain RPC methods (eth_call, eth_getBalance, eth_sendTransaction, etc.) as MCP tools that can be called by Claude and other MCP clients. Implements a schema-based tool registry that maps Alchemy's JSON-RPC API surface to MCP's standardized tool-calling interface, handling parameter validation, request serialization, and response deserialization transparently.

Solves for

Call blockchain read methods like eth_getBalance or eth_call without manually constructing JSON-RPC requestsExecute blockchain write operations (eth_sendTransaction) through an MCP-compatible interfaceIntegrate Alchemy blockchain queries into Claude conversations or agentic workflowsAccess Alchemy-specific enhanced APIs (alchemy_getTokenBalances, alchemy_getNFTs) through standard MCP tool calling

Best for

AI agents and Claude instances that need blockchain data access

Developers building LLM-powered dApps or blockchain analysis tools

Teams integrating Alchemy infrastructure into agentic workflows

Requires

Alchemy API key (free tier available)

MCP client implementation (Claude Desktop, custom MCP client, or compatible tool)

Node.js 16+ for running the MCP server

Limitations

Requires valid Alchemy API key; rate limits apply per Alchemy plan tier

Network latency depends on Alchemy endpoint availability and blockchain congestion

No built-in transaction simulation or gas estimation — raw RPC methods only

What makes it unique

Bridges Alchemy's full JSON-RPC API surface directly into MCP's tool-calling protocol without requiring developers to write custom tool definitions; handles Alchemy-specific enhanced methods (alchemy_getTokenBalances, alchemy_getNFTs) alongside standard Ethereum RPC, providing a unified interface for blockchain data access in agentic contexts.

vs alternatives

Simpler than building custom Claude tools for each Alchemy method and more feature-complete than generic Ethereum RPC MCP servers because it exposes Alchemy's proprietary enhanced APIs (token/NFT data, transaction simulation) natively.

multi-chain network abstraction and routing

Medium confidence

Abstracts blockchain network selection by mapping network identifiers (mainnet, sepolia, polygon, arbitrum, etc.) to Alchemy endpoints, allowing MCP clients to specify target chains without managing endpoint URLs. Implements a configuration layer that routes RPC calls to the correct Alchemy endpoint based on network context, supporting both EVM and non-EVM chains that Alchemy serves.

Solves for

Query data from multiple blockchain networks (Ethereum, Polygon, Arbitrum, Optimism) in a single agent sessionSwitch between mainnet and testnet without reconfiguring endpointsBuild chain-agnostic blockchain agents that work across multiple networks

Best for

Multi-chain dApp developers and blockchain analysts

Agents that need to compare data or execute transactions across different blockchains

Teams building cross-chain orchestration tools

Requires

Alchemy API key with access to desired networks

MCP client capable of passing network context in tool parameters

Limitations

Limited to networks supported by Alchemy (does not support all EVM chains or non-EVM blockchains)

No automatic chain detection or validation — client must specify network explicitly

No cross-chain atomic operations or bridge abstractions

What makes it unique

Provides transparent network routing within the MCP protocol layer, allowing clients to specify chains as parameters rather than managing separate tool instances per network; integrates Alchemy's multi-chain endpoint infrastructure directly into the MCP tool registry.

vs alternatives

More convenient than managing separate MCP servers per blockchain network and more flexible than hardcoded single-chain RPC tools because it centralizes network routing logic in one server instance.

alchemy enhanced api exposure (token and nft data)

Medium confidence

Wraps Alchemy's proprietary enhanced APIs (alchemy_getTokenBalances, alchemy_getNFTs, alchemy_getAssetTransfers, alchemy_getOwnersForToken) as MCP tools, providing high-level blockchain data queries without requiring clients to parse raw contract state or construct complex filter logic. These methods abstract away contract interaction complexity and return pre-indexed, normalized data from Alchemy's infrastructure.

Solves for

Retrieve all token balances for a wallet address without querying individual token contractsFetch NFT collections and metadata for an address in a single callQuery asset transfer history with filtering by token type, time range, or directionFind all token holders or owners of a specific NFT collection

Best for

Portfolio tracking and wallet analysis agents

NFT discovery and collection analysis tools

Blockchain data aggregation and reporting applications

Requires

Alchemy API key with enhanced API access enabled

Target blockchain must be indexed by Alchemy (Ethereum, Polygon, Arbitrum, Optimism, etc.)

Limitations

Data freshness depends on Alchemy's indexing latency (typically seconds to minutes behind chain tip)

Metadata quality depends on on-chain data and Alchemy's enrichment; some tokens/NFTs may have incomplete metadata

No real-time streaming; queries return point-in-time snapshots

What makes it unique

Exposes Alchemy's proprietary indexed data APIs (not available through standard Ethereum RPC) as first-class MCP tools, allowing agents to query normalized token and NFT data without implementing custom indexing or contract parsing logic.

vs alternatives

More efficient than building agents that call raw eth_call methods to query token balances or NFT ownership because it leverages Alchemy's pre-indexed data; provides richer metadata than generic blockchain RPC servers.

mcp server lifecycle management and configuration

Medium confidence

Implements standard MCP server initialization, configuration loading, and resource management. Handles MCP protocol handshake, tool registry initialization, and graceful shutdown. Supports environment-based configuration (API keys, network settings) and exposes Alchemy API credentials securely through the MCP server process without leaking them to clients.

Solves for

Start an MCP server that Claude Desktop or other MCP clients can discover and connect toConfigure Alchemy API credentials and network preferences at server startupManage server lifecycle (startup, shutdown, error handling) in production environments

Best for

Developers deploying Alchemy MCP servers in local or cloud environments

Teams integrating Alchemy into Claude Desktop or custom MCP client setups

DevOps engineers managing MCP infrastructure

Requires

Node.js 16+ runtime

Alchemy API key in environment variable (ALCHEMY_API_KEY)

MCP client implementation or Claude Desktop with MCP support

Limitations

Configuration is static at server startup; no hot-reload of API keys or network settings

No built-in authentication or authorization between MCP clients and server (assumes trusted network)

Single-process server; no horizontal scaling or load balancing

What makes it unique

Implements the full MCP server specification for Alchemy, handling protocol compliance, tool registry initialization, and secure credential management within the server process boundary.

vs alternatives

Simpler than building a custom MCP server from scratch because it provides pre-built lifecycle management and Alchemy-specific tool definitions; more secure than passing API keys directly to clients because credentials stay server-side.

error handling and rpc failure recovery

Medium confidence

Implements error handling for blockchain RPC failures, network timeouts, and invalid parameters. Maps Alchemy-specific error codes and JSON-RPC errors to human-readable MCP error responses. Provides retry logic for transient failures (network timeouts, temporary endpoint unavailability) while failing fast on permanent errors (invalid addresses, insufficient gas).

Solves for

Handle RPC errors gracefully without crashing the agent or MCP serverDistinguish between transient network failures and permanent blockchain errorsProvide clear error messages to agents so they can decide whether to retry or escalate

Best for

Production agents that need resilience to blockchain network instability

Teams building mission-critical blockchain applications

Developers debugging blockchain integration issues

Requires

MCP client capable of handling error responses

Alchemy API key with appropriate permissions for target methods

Limitations

Retry logic is basic (fixed backoff, limited retry count); no exponential backoff or circuit breaker pattern

Error classification depends on Alchemy's error response format; non-standard errors may not be handled correctly

No observability hooks (logging, metrics) built into the MCP server; error tracking requires external instrumentation

What makes it unique

Provides Alchemy-specific error handling that understands blockchain-domain failures (invalid addresses, contract reverts, gas estimation errors) and maps them to MCP error responses, rather than generic HTTP error handling.

vs alternatives

More robust than naive RPC proxies that fail on any error because it implements retry logic and error classification; more transparent than black-box error handling because it exposes error details to agents.

schema-based tool parameter validation

Medium confidence

Validates MCP tool parameters against JSON schemas derived from Alchemy's RPC method signatures. Checks parameter types, required fields, and value constraints (e.g., valid hex addresses, block numbers) before sending requests to Alchemy. Provides detailed validation error messages to clients, preventing invalid RPC calls and reducing wasted API quota.

Solves for

Catch invalid parameters (malformed addresses, wrong types) before sending to AlchemyProvide agents with clear feedback about what parameters are required or invalidReduce API quota waste by filtering invalid requests client-side

Best for

Agents that need strict parameter validation before blockchain calls

Teams with limited Alchemy API quota who want to minimize wasted calls

Developers debugging parameter-related RPC failures

Requires

MCP client that respects tool schemas

Alchemy RPC method schemas (provided by MCP server)

Limitations

Validation is schema-based and may not catch all semantic errors (e.g., calling a non-existent contract address is valid syntax but fails at runtime)

Schema maintenance required if Alchemy RPC API changes

No custom validation logic; limited to JSON schema constraints

What makes it unique

Implements JSON schema-based validation for Alchemy RPC parameters within the MCP tool registry, preventing invalid calls before they reach Alchemy's endpoints.

vs alternatives

More efficient than letting invalid calls fail at Alchemy because it catches errors earlier and provides better error messages; more maintainable than custom validation code because it uses standard JSON schemas.

transaction construction and signing preparation

Medium confidence

Provides MCP tools for constructing unsigned transaction objects that conform to Ethereum standards (EIP-1559, legacy transactions). Accepts transaction parameters (to, from, value, data, gas, gasPrice) and returns a serialized transaction object ready for signing. Does not perform signing itself (that remains client responsibility) but validates transaction structure and estimates gas if requested.

Solves for

Build transaction objects for agents to sign and broadcastEstimate gas costs for proposed transactions before signingConstruct contract interaction transactions (encoded function calls) for agents

Best for

Agents that need to construct and execute blockchain transactions

Wallets or signing services that integrate with Alchemy for transaction building

Teams building transaction simulation or dry-run tools

Requires

Alchemy API key with eth_estimateGas access

Valid Ethereum addresses and transaction parameters

Limitations

Does not perform signing; clients must handle key management and signing separately

Gas estimation depends on current network state; estimates may become stale if not used immediately

No built-in nonce management; clients must track and provide nonces

What makes it unique

Integrates Alchemy's gas estimation and transaction validation into the MCP tool layer, allowing agents to construct and validate transactions without implementing Ethereum transaction encoding logic.

vs alternatives

Simpler than agents implementing their own transaction encoding because it provides pre-built transaction construction tools; more flexible than hardcoded transaction templates because it accepts arbitrary parameters.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with @alchemy/mcp-server, ranked by overlap. Discovered automatically through the match graph.

MCP Server29

@alchemy/mcp-server

MCP server for using Alchemy APIs

blockchain-native rpc method exposure via mcp protocolmulti-chain rpc endpoint routingalchemy-specific enhanced rpc methods (enhanced apis)alchemy api key management and request signing

4 shared capabilities

MCP Server25

Thirdweb

** - Read/write to over 2k blockchains, enabling data querying, contract analysis/deployment, and transaction execution, powered by [Thirdweb](https://thirdweb.com/)

multi-chain data querying across 2000+ blockchainstransaction execution and monitoring

2 shared capabilities

MCP Server21

@moralisweb3/api-mcp-server

Moralis MCP server

blockchain-data-query-via-mcp-protocolmulti-chain-blockchain-query-routing

2 shared capabilities

MCP Server26

Hive Intelligence

** 📇 ☁️ 🏠 - Hive Intelligence: Ultimate cryptocurrency MCP for AI assistants with unified access to crypto, DeFi, and Web3 analytics. Hive's remote mcp server guide [remote server](https://hiveintelligence.xyz/crypto-mcp).

multi-chain-token-bridge-and-swap-routingdefi-protocol-interaction-via-mcp

2 shared capabilities

MCP Server25

Nebula-Block-Data/nebulablock-mcp-server

** integrates with the fastmcp library to expose the full range of NebulaBlock API functionalities as accessible tools

multi-blockchain-data-aggregation-via-toolsblockchain-data-query-via-mcp-tools

2 shared capabilities

MCP Server24

Openfort

** - Supercharge your AI assistant with plug-and-play access to authentication, project scaffolding, and smart wallet tooling.

mcp-based wallet authentication integrationmulti-provider blockchain rpc abstraction

2 shared capabilities

Best For

✓AI agents and Claude instances that need blockchain data access
✓Developers building LLM-powered dApps or blockchain analysis tools
✓Teams integrating Alchemy infrastructure into agentic workflows
✓Multi-chain dApp developers and blockchain analysts
✓Agents that need to compare data or execute transactions across different blockchains
✓Teams building cross-chain orchestration tools
✓Portfolio tracking and wallet analysis agents
✓NFT discovery and collection analysis tools

Known Limitations

⚠Requires valid Alchemy API key; rate limits apply per Alchemy plan tier
⚠Network latency depends on Alchemy endpoint availability and blockchain congestion
⚠No built-in transaction simulation or gas estimation — raw RPC methods only
⚠Synchronous request/response model; no streaming for long-running blockchain operations
⚠Limited to networks supported by Alchemy (does not support all EVM chains or non-EVM blockchains)
⚠No automatic chain detection or validation — client must specify network explicitly

Requirements

Alchemy API key (free tier available)MCP client implementation (Claude Desktop, custom MCP client, or compatible tool)Node.js 16+ for running the MCP serverNetwork connectivity to Alchemy endpointsAlchemy API key with access to desired networksMCP client capable of passing network context in tool parametersAlchemy API key with enhanced API access enabledTarget blockchain must be indexed by Alchemy (Ethereum, Polygon, Arbitrum, Optimism, etc.)

Input / Output

Accepts: JSON-RPC method names (strings), Method parameters (addresses, contract ABIs, transaction objects, block identifiers), Blockchain network identifiers (mainnet, sepolia, polygon, etc.), Network identifiers (strings: 'mainnet', 'sepolia', 'polygon', 'arbitrum', etc.), RPC method parameters specific to target network, Wallet addresses (hex strings), Token contract addresses, Filter parameters (token type, time range, transfer direction), Pagination cursors, Environment variables (API key, network configuration), MCP protocol messages (tool calls, resource requests), RPC method calls that may fail, Network conditions (timeouts, connection errors), Tool parameters (addresses, block numbers, transaction objects, etc.), Transaction parameters (to, from, value, data, gas, gasPrice, nonce), Contract ABIs and function signatures for encoding calls

Produces: JSON-RPC responses (hex-encoded values, transaction hashes, decoded data), Structured blockchain data (balances, transaction receipts, contract state), Network-specific blockchain data (balances, transactions, contract state), Token balance objects (address, balance, decimals, symbol, logo), NFT metadata objects (contract address, token ID, name, image, attributes), Transfer history arrays with timestamps and amounts, MCP protocol responses (tool results, error messages), Server status and health indicators, MCP error responses with error codes and messages, Retry signals or failure indicators, Validation success/failure responses, Detailed error messages describing validation failures, Unsigned transaction objects (serialized or structured), Gas estimation results (wei)

UnfragileRank

Adoption30%(25% weight)

Quality14%(25% weight)

Ecosystem52%(15% weight)

Match Graph25%(30% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

7 capabilities

Visit @alchemy/mcp-server→

Repository Details

Package Details

npm

Registry

0.3.0

Version

1,631

Weekly Downloads

About

MCP server for using Alchemy APIs

Alternatives to @alchemy/mcp-server

LangChain72Framework

Revolutionize AI application development, monitoring, and...

Compare →

Bubble AI71Product

No-code AI app builder from natural language.

Compare →

LlamaIndex70Framework

Transform enterprise data into powerful LLM applications...

Compare →

Glide70Product

No-code app builder from spreadsheets — AI-generated mobile and web apps.

Compare →

Are you the builder of @alchemy/mcp-server?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

npm

Looking for something else?

Search →

Capabilities7 decomposed

blockchain rpc method invocation via mcp protocol

Medium confidence

Solves for

Best for

AI agents and Claude instances that need blockchain data access

Developers building LLM-powered dApps or blockchain analysis tools

Teams integrating Alchemy infrastructure into agentic workflows

Requires

Alchemy API key (free tier available)

MCP client implementation (Claude Desktop, custom MCP client, or compatible tool)

Node.js 16+ for running the MCP server

Limitations

Requires valid Alchemy API key; rate limits apply per Alchemy plan tier

Network latency depends on Alchemy endpoint availability and blockchain congestion

No built-in transaction simulation or gas estimation — raw RPC methods only

What makes it unique

vs alternatives

multi-chain network abstraction and routing

Medium confidence

Solves for

Best for

Multi-chain dApp developers and blockchain analysts

Agents that need to compare data or execute transactions across different blockchains

Teams building cross-chain orchestration tools

Requires

Alchemy API key with access to desired networks

MCP client capable of passing network context in tool parameters

Limitations

Limited to networks supported by Alchemy (does not support all EVM chains or non-EVM blockchains)

No automatic chain detection or validation — client must specify network explicitly

No cross-chain atomic operations or bridge abstractions

What makes it unique

vs alternatives

More convenient than managing separate MCP servers per blockchain network and more flexible than hardcoded single-chain RPC tools because it centralizes network routing logic in one server instance.

alchemy enhanced api exposure (token and nft data)

Medium confidence

Solves for

Best for

Portfolio tracking and wallet analysis agents

NFT discovery and collection analysis tools

Blockchain data aggregation and reporting applications

Requires

Alchemy API key with enhanced API access enabled

Target blockchain must be indexed by Alchemy (Ethereum, Polygon, Arbitrum, Optimism, etc.)

Limitations

Data freshness depends on Alchemy's indexing latency (typically seconds to minutes behind chain tip)

Metadata quality depends on on-chain data and Alchemy's enrichment; some tokens/NFTs may have incomplete metadata

No real-time streaming; queries return point-in-time snapshots

What makes it unique

vs alternatives

mcp server lifecycle management and configuration

Medium confidence

Solves for

Best for

Developers deploying Alchemy MCP servers in local or cloud environments

Teams integrating Alchemy into Claude Desktop or custom MCP client setups

DevOps engineers managing MCP infrastructure

Requires

Node.js 16+ runtime

Alchemy API key in environment variable (ALCHEMY_API_KEY)

MCP client implementation or Claude Desktop with MCP support

Limitations

Configuration is static at server startup; no hot-reload of API keys or network settings

No built-in authentication or authorization between MCP clients and server (assumes trusted network)

Single-process server; no horizontal scaling or load balancing

What makes it unique

Implements the full MCP server specification for Alchemy, handling protocol compliance, tool registry initialization, and secure credential management within the server process boundary.

vs alternatives

error handling and rpc failure recovery

Medium confidence

Solves for

Best for

Production agents that need resilience to blockchain network instability

Teams building mission-critical blockchain applications

Developers debugging blockchain integration issues

Requires

MCP client capable of handling error responses

Alchemy API key with appropriate permissions for target methods

Limitations

Retry logic is basic (fixed backoff, limited retry count); no exponential backoff or circuit breaker pattern

Error classification depends on Alchemy's error response format; non-standard errors may not be handled correctly

No observability hooks (logging, metrics) built into the MCP server; error tracking requires external instrumentation

What makes it unique

vs alternatives

schema-based tool parameter validation

Medium confidence

Solves for

Best for

Agents that need strict parameter validation before blockchain calls

Teams with limited Alchemy API quota who want to minimize wasted calls

Developers debugging parameter-related RPC failures

Requires

MCP client that respects tool schemas

Alchemy RPC method schemas (provided by MCP server)

Limitations

Validation is schema-based and may not catch all semantic errors (e.g., calling a non-existent contract address is valid syntax but fails at runtime)

Schema maintenance required if Alchemy RPC API changes

No custom validation logic; limited to JSON schema constraints

What makes it unique

Implements JSON schema-based validation for Alchemy RPC parameters within the MCP tool registry, preventing invalid calls before they reach Alchemy's endpoints.

vs alternatives

transaction construction and signing preparation

Medium confidence

Solves for

Build transaction objects for agents to sign and broadcastEstimate gas costs for proposed transactions before signingConstruct contract interaction transactions (encoded function calls) for agents

Best for

Agents that need to construct and execute blockchain transactions

Wallets or signing services that integrate with Alchemy for transaction building

Teams building transaction simulation or dry-run tools

Requires

Alchemy API key with eth_estimateGas access

Valid Ethereum addresses and transaction parameters

Limitations

Does not perform signing; clients must handle key management and signing separately

Gas estimation depends on current network state; estimates may become stale if not used immediately

No built-in nonce management; clients must track and provide nonces

What makes it unique

vs alternatives

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to @alchemy/mcp-server

LangChain72Framework

Revolutionize AI application development, monitoring, and...

Compare →

Bubble AI71Product

No-code AI app builder from natural language.

Compare →

LlamaIndex70Framework

Transform enterprise data into powerful LLM applications...

Compare →

Glide70Product

No-code app builder from spreadsheets — AI-generated mobile and web apps.

Compare →

@alchemy/mcp-server

Capabilities7 decomposed

blockchain rpc method invocation via mcp protocol

multi-chain network abstraction and routing

alchemy enhanced api exposure (token and nft data)

mcp server lifecycle management and configuration

error handling and rpc failure recovery

schema-based tool parameter validation

transaction construction and signing preparation

Related Artifactssharing capabilities

@alchemy/mcp-server

Thirdweb

@moralisweb3/api-mcp-server

Hive Intelligence

Nebula-Block-Data/nebulablock-mcp-server

Openfort

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

Package Details

About

Categories

Alternatives to @alchemy/mcp-server

Are you the builder of @alchemy/mcp-server?

Get the weekly brief

Data Sources

@alchemy/mcp-server

Capabilities7 decomposed

blockchain rpc method invocation via mcp protocol

multi-chain network abstraction and routing

alchemy enhanced api exposure (token and nft data)

mcp server lifecycle management and configuration

error handling and rpc failure recovery

schema-based tool parameter validation

transaction construction and signing preparation

Related Artifactssharing capabilities

@alchemy/mcp-server

Thirdweb

@moralisweb3/api-mcp-server

Hive Intelligence

Nebula-Block-Data/nebulablock-mcp-server

Openfort

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

Package Details

About

Categories

Alternatives to @alchemy/mcp-server

Are you the builder of @alchemy/mcp-server?

Get the weekly brief

Data Sources