{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-alchemymcp-server","slug":"npm-alchemymcp-server","name":"@alchemy/mcp-server","type":"mcp","url":"https://www.npmjs.com/package/@alchemy/mcp-server","page_url":"https://unfragile.ai/npm-alchemymcp-server","categories":["mcp-servers"],"tags":["alchemy","mcp","model-context-protocol","blockchain"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-alchemymcp-server__cap_0","uri":"capability://tool.use.integration.blockchain.native.rpc.method.exposure.via.mcp.protocol","name":"blockchain-native rpc method exposure via mcp protocol","description":"Exposes Alchemy's blockchain RPC methods (eth_call, eth_sendTransaction, eth_getBalance, etc.) as standardized MCP tools that Claude and other MCP clients can invoke. Implements the Model Context Protocol specification to translate Alchemy API endpoints into a tool registry with JSON schema validation, enabling LLM agents to interact with blockchain state without direct HTTP knowledge.","intents":["I want my Claude agent to read blockchain data like account balances and contract state without writing custom API wrappers","I need to enable LLM-driven blockchain transactions through a standardized protocol instead of building custom integrations","I want to abstract away Alchemy API authentication and RPC method signatures so agents can focus on logic"],"best_for":["AI agent developers building blockchain-aware applications","Teams integrating Claude with Web3 workflows","Builders prototyping LLM-driven DeFi or NFT applications"],"limitations":["Limited to Alchemy's supported RPC methods — custom contract ABIs require separate schema definition","No built-in transaction simulation or dry-run capability — agents must handle transaction validation externally","Synchronous RPC calls only — no streaming or subscription-based event listening","No rate-limiting or quota management at the MCP layer — relies on Alchemy account limits"],"requires":["Alchemy API key with appropriate permissions","MCP-compatible client (Claude Desktop, or custom MCP host)","Node.js 16+ runtime","Network access to Alchemy endpoints"],"input_types":["JSON-formatted RPC parameters (addresses, transaction hashes, contract data)","Blockchain identifiers (chain IDs, block numbers, transaction hashes)"],"output_types":["JSON RPC responses (account balances, transaction receipts, contract state)","Structured blockchain data (block headers, transaction objects, logs)"],"categories":["tool-use-integration","blockchain-api"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-alchemymcp-server__cap_1","uri":"capability://tool.use.integration.alchemy.specific.enhanced.rpc.methods.enhanced.apis","name":"alchemy-specific enhanced rpc methods (enhanced apis)","description":"Exposes Alchemy's proprietary Enhanced APIs (alchemy_getTokenBalances, alchemy_getNFTs, alchemy_getAssetTransfers, etc.) as MCP tools with pre-configured schemas. These methods provide higher-level abstractions over raw Ethereum RPC, returning parsed and indexed blockchain data without requiring agents to manually decode contract ABIs or filter logs.","intents":["I want my agent to fetch all NFTs owned by an address without manually querying ERC-721 contracts","I need to retrieve token balances across multiple ERC-20 contracts in a single call","I want to analyze asset transfer history for an address without parsing raw transaction logs"],"best_for":["NFT and DeFi application builders using Claude agents","Teams building portfolio tracking or wallet analysis tools","Developers prototyping token discovery and asset management features"],"limitations":["Enhanced APIs only available on Alchemy's premium plans — free tier limited to standard RPC","Data freshness depends on Alchemy's indexing latency — typically 1-2 blocks behind chain head","No custom filtering at the MCP layer — agents must post-process results for complex queries","Limited to Alchemy's supported chains (Ethereum, Polygon, Arbitrum, Optimism, etc.) — no cross-chain aggregation"],"requires":["Alchemy API key with Enhanced API access enabled","Alchemy premium or growth tier subscription","MCP-compatible client","Node.js 16+"],"input_types":["Ethereum addresses (checksummed or lowercase)","Contract addresses","Block range parameters (fromBlock, toBlock)"],"output_types":["Parsed token balance objects with decimals and metadata","NFT metadata arrays with image URIs and attributes","Transfer history with decoded transaction details"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-alchemymcp-server__cap_2","uri":"capability://tool.use.integration.mcp.tool.schema.auto.generation.from.alchemy.method.signatures","name":"mcp tool schema auto-generation from alchemy method signatures","description":"Automatically generates MCP-compliant tool schemas (JSON Schema format) from Alchemy's RPC and Enhanced API method signatures, including parameter validation, type coercion, and error handling. Implements schema introspection to map Alchemy's API documentation into structured tool definitions that MCP clients can parse and present to LLMs with proper type hints and constraints.","intents":["I want Claude to understand the exact parameters and return types for Alchemy methods without manual schema definition","I need type validation on blockchain parameters (addresses, hashes, block numbers) before sending to Alchemy","I want error messages from Alchemy to be translated into human-readable guidance for the agent"],"best_for":["MCP server developers building blockchain integrations","Teams automating tool definition maintenance","Builders reducing manual schema boilerplate"],"limitations":["Schema generation limited to documented Alchemy methods — custom or beta endpoints require manual definition","Type coercion assumes standard Ethereum types (address, uint256, bytes32) — complex struct types may require custom handlers","No runtime validation of blockchain-specific constraints (e.g., address checksums, valid block ranges) — validation is schema-level only","Error schema generation depends on Alchemy's documented error responses — undocumented errors may not be properly typed"],"requires":["Alchemy API documentation or OpenAPI spec","Node.js 16+","JSON Schema validator library"],"input_types":["Alchemy API method signatures","Parameter metadata (types, required fields, constraints)"],"output_types":["JSON Schema objects for MCP tool definitions","Typed parameter validation rules","Error response schemas"],"categories":["tool-use-integration","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-alchemymcp-server__cap_3","uri":"capability://tool.use.integration.alchemy.api.key.management.and.request.signing","name":"alchemy api key management and request signing","description":"Handles secure storage and injection of Alchemy API keys into outbound RPC requests, implementing request signing and authentication headers required by Alchemy's endpoints. Manages API key lifecycle (rotation, expiration) and enforces rate-limiting headers to prevent quota exhaustion, abstracting authentication complexity from MCP clients.","intents":["I want my MCP server to securely use my Alchemy API key without exposing it to the client","I need to rotate API keys without restarting the MCP server","I want to monitor and enforce rate limits to avoid exceeding my Alchemy quota"],"best_for":["Production deployments of blockchain agents","Teams managing multiple Alchemy API keys across environments","Builders requiring audit trails of API usage"],"limitations":["API key stored in environment variables or config files — no built-in key vault integration (AWS Secrets Manager, HashiCorp Vault)","Rate limiting enforced at MCP server level only — no cross-instance coordination for distributed deployments","No request caching — every MCP tool invocation results in a fresh Alchemy API call","Key rotation requires server restart or manual refresh — no hot-reload capability"],"requires":["Alchemy API key (stored as environment variable or config)","Node.js 16+","Network access to Alchemy endpoints"],"input_types":["API key string","Rate limit configuration (requests per second)"],"output_types":["Authenticated HTTP requests to Alchemy","Rate limit status and remaining quota"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-alchemymcp-server__cap_4","uri":"capability://tool.use.integration.multi.chain.rpc.endpoint.routing","name":"multi-chain rpc endpoint routing","description":"Routes MCP tool calls to the appropriate Alchemy RPC endpoint based on chain ID or network name (Ethereum mainnet, Polygon, Arbitrum, Optimism, etc.). Implements chain detection logic to automatically select the correct endpoint and validate that requested operations are supported on the target chain, enabling agents to work across multiple blockchains through a unified MCP interface.","intents":["I want my agent to query data from Polygon without manually switching RPC endpoints","I need to detect which chain a contract address belongs to and route the call correctly","I want to support multi-chain operations (e.g., compare token prices across Ethereum and Polygon) through a single MCP interface"],"best_for":["Multi-chain DeFi and NFT application developers","Teams building cross-chain analytics or arbitrage agents","Builders supporting users across multiple blockchain ecosystems"],"limitations":["Chain routing limited to Alchemy's supported networks — no custom RPC endpoint configuration","No cross-chain atomic operations — agents must handle multi-chain transactions as separate calls","Chain detection relies on explicit chain ID parameter — no automatic chain inference from addresses","No built-in bridge or swap routing — agents must use separate tools for cross-chain asset movement"],"requires":["Alchemy API keys for each supported chain","Chain ID or network name parameter in tool calls","Node.js 16+"],"input_types":["Chain ID (integer: 1 for Ethereum, 137 for Polygon, etc.)","Network name string (ethereum, polygon, arbitrum, optimism)"],"output_types":["RPC responses from the selected chain endpoint","Chain metadata (network name, currency, block time)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-alchemymcp-server__cap_5","uri":"capability://tool.use.integration.transaction.simulation.and.dry.run.execution","name":"transaction simulation and dry-run execution","description":"Leverages Alchemy's simulation APIs (eth_call, eth_simulateExecution) to execute transactions in a read-only sandbox before broadcasting to the network. Returns detailed execution traces including gas usage, state changes, and revert reasons, enabling agents to validate transaction logic and estimate costs without risking real assets or network fees.","intents":["I want my agent to test a transaction before sending it to avoid wasting gas on failed transactions","I need to estimate gas costs for a complex smart contract interaction","I want to understand why a transaction would fail before broadcasting it"],"best_for":["DeFi agents executing complex transactions (swaps, liquidity provision, lending)","Teams building transaction builders or simulators","Developers prototyping smart contract interactions"],"limitations":["Simulation accuracy depends on contract state at simulation block — state may diverge by execution time","No support for multi-block simulations — agents cannot simulate time-dependent logic (e.g., staking rewards)","Simulation results do not account for mempool ordering or MEV — actual execution may differ","Complex contract interactions may timeout if simulation depth exceeds Alchemy's limits"],"requires":["Alchemy API key with simulation API access","Transaction object (to, data, value, from, gas)","Node.js 16+"],"input_types":["Transaction objects (Ethereum transaction format)","Block number for state snapshot (defaults to latest)"],"output_types":["Execution trace with gas usage","State changes (storage updates, balance changes)","Revert reason and error messages"],"categories":["tool-use-integration","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-alchemymcp-server__cap_6","uri":"capability://automation.workflow.webhook.based.event.streaming.and.indexing","name":"webhook-based event streaming and indexing","description":"Configures Alchemy Notify webhooks to stream blockchain events (transfers, contract interactions, state changes) to the MCP server, which indexes and caches events for agent queries. Implements event filtering, deduplication, and persistence, enabling agents to react to real-time blockchain activity without polling or maintaining their own event listeners.","intents":["I want my agent to be notified when a specific wallet receives a transfer","I need to monitor contract events (e.g., Uniswap swaps) and trigger actions based on conditions","I want to build an event-driven agent that reacts to blockchain activity in real-time"],"best_for":["Real-time blockchain monitoring and alerting agents","Teams building event-driven DeFi applications","Developers creating automated trading or arbitrage bots"],"limitations":["Webhook delivery is asynchronous and not guaranteed — events may be missed or delayed","Event indexing requires persistent storage — no built-in database, requires external state store (Redis, PostgreSQL)","Webhook configuration requires manual setup in Alchemy dashboard — no programmatic webhook management in MCP server","Event filtering limited to Alchemy's supported event types — custom contract events require manual ABI parsing"],"requires":["Alchemy Notify subscription (paid feature)","Public URL for webhook endpoint (requires server to be internet-accessible)","Persistent storage backend (Redis, PostgreSQL, or similar)","Node.js 16+"],"input_types":["Event filter configuration (contract address, event signature, address)","Webhook payload from Alchemy (event data, transaction details)"],"output_types":["Indexed event records with metadata","Event query results (filtered by address, contract, time range)","Real-time event notifications to agents"],"categories":["automation-workflow","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-alchemymcp-server__cap_7","uri":"capability://code.generation.editing.contract.abi.parsing.and.function.encoding","name":"contract abi parsing and function encoding","description":"Parses contract ABIs (Application Binary Interfaces) to automatically generate MCP tools for contract functions, handling parameter encoding, return value decoding, and error handling. Implements ethers.js or web3.js integration to convert human-readable function calls into encoded transaction data (calldata) and decode return values, enabling agents to interact with smart contracts without manual ABI knowledge.","intents":["I want my agent to call a smart contract function without manually encoding parameters","I need to decode contract return values into readable format","I want to generate MCP tools from a contract ABI automatically"],"best_for":["DeFi and NFT application developers","Teams building contract interaction agents","Builders reducing manual calldata encoding complexity"],"limitations":["ABI parsing assumes standard Solidity ABI format — non-standard or proxy contract ABIs may require manual handling","Complex types (nested structs, arrays of tuples) may not encode/decode correctly without custom handlers","No automatic function discovery — agents must provide ABI explicitly","Error decoding limited to standard Solidity errors — custom error types require manual definition"],"requires":["Contract ABI (JSON format)","ethers.js or web3.js library","Node.js 16+"],"input_types":["Contract ABI (JSON array of function/event definitions)","Function name and parameters (human-readable format)"],"output_types":["Encoded calldata (hex string)","Decoded return values (typed objects)","MCP tool definitions for contract functions"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":32,"verified":false,"data_access_risk":"high","permissions":["Alchemy API key with appropriate permissions","MCP-compatible client (Claude Desktop, or custom MCP host)","Node.js 16+ runtime","Network access to Alchemy endpoints","Alchemy API key with Enhanced API access enabled","Alchemy premium or growth tier subscription","MCP-compatible client","Node.js 16+","Alchemy API documentation or OpenAPI spec","JSON Schema validator library"],"failure_modes":["Limited to Alchemy's supported RPC methods — custom contract ABIs require separate schema definition","No built-in transaction simulation or dry-run capability — agents must handle transaction validation externally","Synchronous RPC calls only — no streaming or subscription-based event listening","No rate-limiting or quota management at the MCP layer — relies on Alchemy account limits","Enhanced APIs only available on Alchemy's premium plans — free tier limited to standard RPC","Data freshness depends on Alchemy's indexing latency — typically 1-2 blocks behind chain head","No custom filtering at the MCP layer — agents must post-process results for complex queries","Limited to Alchemy's supported chains (Ethereum, Polygon, Arbitrum, Optimism, etc.) — no cross-chain aggregation","Schema generation limited to documented Alchemy methods — custom or beta endpoints require manual definition","Type coercion assumes standard Ethereum types (address, uint256, bytes32) — complex struct types may require custom handlers","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.30269679134085137,"quality":0.26,"ecosystem":0.42,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.903Z","last_scraped_at":"2026-05-03T14:23:34.173Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":1631,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-alchemymcp-server","compare_url":"https://unfragile.ai/compare?artifact=npm-alchemymcp-server"}},"signature":"DPyCp+qhLP7vmD43GQUxWUCPz+HGOd0ncEnWZiqjBZhQoTdSyKdoT+YMqtevnOsdoCl++LiJpRGcYAs6AE9qDw==","signedAt":"2026-06-20T11:44:13.437Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-alchemymcp-server","artifact":"https://unfragile.ai/npm-alchemymcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=npm-alchemymcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}