@alchemy/mcp-server
Enables Claude to query blockchain data via Alchemy APIs, reducing integration friction for teams building Web3 applications and needing real-time on-chain i…
An MCP server that lets Claude query Alchemy's blockchain APIs directly, with no code. Claude can fetch token prices and price history, NFT ownership and contract data, transaction history and asset transfers, and token balances across multiple networks. Sending transactions and DEX swaps are also supported but require a separately configured wallet agent server.
- Ask Claude to fetch blockchain transaction details using Alchemy API endpoints
- Generate web3 application code that integrates Alchemy for smart contract monitoring
- Automate queries to retrieve token balances and NFT metadata via Alchemy APIs
Enables Claude to query blockchain data via Alchemy APIs, reducing integration friction for teams building Web3 applications and needing real-time on-chain intelligence without custom API wrappers.
Web3 development teams building on Ethereum, Polygon, or other supported chains requiring programmatic blockchain data access.
https://github.com/alchemyplatform/alchemy-mcp-server
By GitHub Actions
How to Get It
npx -y @alchemy/mcp-server
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
Once it’s connected, paste this into Claude:
Fetch blockchain transaction details using Alchemy API endpoints
Trust Signals Auto-scanned
Data & Access
Community Pulse Quiet
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 86 GitHub stars; contributors unknown; last commit 61d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 86 GitHub stars; contributors unknown; last commit 61d ago; license MIT.