{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm-alchemy-mcp-server","slug":"alchemy-mcp-server","name":"@alchemy/mcp-server","type":"mcp","url":"https://github.com/alchemyplatform/alchemy-mcp","page_url":"https://unfragile.ai/alchemy-mcp-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-alchemy-mcp-server__cap_0","uri":"capability://tool.use.integration.blockchain.rpc.method.invocation.via.mcp.protocol","name":"blockchain rpc method invocation via mcp protocol","description":"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.","intents":["Call blockchain read methods like eth_getBalance or eth_call without manually constructing JSON-RPC requests","Execute blockchain write operations (eth_sendTransaction) through an MCP-compatible interface","Integrate Alchemy blockchain queries into Claude conversations or agentic workflows","Access 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"],"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"],"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","Network connectivity to Alchemy endpoints"],"input_types":["JSON-RPC method names (strings)","Method parameters (addresses, contract ABIs, transaction objects, block identifiers)","Blockchain network identifiers (mainnet, sepolia, polygon, etc.)"],"output_types":["JSON-RPC responses (hex-encoded values, transaction hashes, decoded data)","Structured blockchain data (balances, transaction receipts, contract state)"],"categories":["tool-use-integration","blockchain"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-alchemy-mcp-server__cap_1","uri":"capability://tool.use.integration.multi.chain.network.abstraction.and.routing","name":"multi-chain network abstraction and routing","description":"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.","intents":["Query data from multiple blockchain networks (Ethereum, Polygon, Arbitrum, Optimism) in a single agent session","Switch between mainnet and testnet without reconfiguring endpoints","Build 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"],"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"],"requires":["Alchemy API key with access to desired networks","MCP client capable of passing network context in tool parameters"],"input_types":["Network identifiers (strings: 'mainnet', 'sepolia', 'polygon', 'arbitrum', etc.)","RPC method parameters specific to target network"],"output_types":["Network-specific blockchain data (balances, transactions, contract state)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-alchemy-mcp-server__cap_2","uri":"capability://tool.use.integration.alchemy.enhanced.api.exposure.token.and.nft.data","name":"alchemy enhanced api exposure (token and nft data)","description":"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.","intents":["Retrieve all token balances for a wallet address without querying individual token contracts","Fetch NFT collections and metadata for an address in a single call","Query asset transfer history with filtering by token type, time range, or direction","Find 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"],"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","Pagination required for large result sets; no built-in aggregation across pages"],"requires":["Alchemy API key with enhanced API access enabled","Target blockchain must be indexed by Alchemy (Ethereum, Polygon, Arbitrum, Optimism, etc.)"],"input_types":["Wallet addresses (hex strings)","Token contract addresses","Filter parameters (token type, time range, transfer direction)","Pagination cursors"],"output_types":["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"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-alchemy-mcp-server__cap_3","uri":"capability://automation.workflow.mcp.server.lifecycle.management.and.configuration","name":"mcp server lifecycle management and configuration","description":"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.","intents":["Start an MCP server that Claude Desktop or other MCP clients can discover and connect to","Configure Alchemy API credentials and network preferences at server startup","Manage 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"],"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","Credentials must be passed via environment variables; no secrets management integration"],"requires":["Node.js 16+ runtime","Alchemy API key in environment variable (ALCHEMY_API_KEY)","MCP client implementation or Claude Desktop with MCP support"],"input_types":["Environment variables (API key, network configuration)","MCP protocol messages (tool calls, resource requests)"],"output_types":["MCP protocol responses (tool results, error messages)","Server status and health indicators"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-alchemy-mcp-server__cap_4","uri":"capability://automation.workflow.error.handling.and.rpc.failure.recovery","name":"error handling and rpc failure recovery","description":"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).","intents":["Handle RPC errors gracefully without crashing the agent or MCP server","Distinguish between transient network failures and permanent blockchain errors","Provide 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"],"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"],"requires":["MCP client capable of handling error responses","Alchemy API key with appropriate permissions for target methods"],"input_types":["RPC method calls that may fail","Network conditions (timeouts, connection errors)"],"output_types":["MCP error responses with error codes and messages","Retry signals or failure indicators"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-alchemy-mcp-server__cap_5","uri":"capability://tool.use.integration.schema.based.tool.parameter.validation","name":"schema-based tool parameter validation","description":"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.","intents":["Catch invalid parameters (malformed addresses, wrong types) before sending to Alchemy","Provide agents with clear feedback about what parameters are required or invalid","Reduce 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"],"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"],"requires":["MCP client that respects tool schemas","Alchemy RPC method schemas (provided by MCP server)"],"input_types":["Tool parameters (addresses, block numbers, transaction objects, etc.)"],"output_types":["Validation success/failure responses","Detailed error messages describing validation failures"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-alchemy-mcp-server__cap_6","uri":"capability://tool.use.integration.transaction.construction.and.signing.preparation","name":"transaction construction and signing preparation","description":"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.","intents":["Build transaction objects for agents to sign and broadcast","Estimate gas costs for proposed transactions before signing","Construct 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"],"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","Limited to standard transaction types; no support for advanced transaction types (bundles, flashbots, etc.)"],"requires":["Alchemy API key with eth_estimateGas access","Valid Ethereum addresses and transaction parameters"],"input_types":["Transaction parameters (to, from, value, data, gas, gasPrice, nonce)","Contract ABIs and function signatures for encoding calls"],"output_types":["Unsigned transaction objects (serialized or structured)","Gas estimation results (wei)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":33,"verified":false,"data_access_risk":"moderate","permissions":["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","Network connectivity to Alchemy endpoints","Alchemy API key with access to desired networks","MCP client capable of passing network context in tool parameters","Alchemy API key with enhanced API access enabled","Target blockchain must be indexed by Alchemy (Ethereum, Polygon, Arbitrum, Optimism, etc.)","Node.js 16+ runtime","Alchemy API key in environment variable (ALCHEMY_API_KEY)"],"failure_modes":["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","No cross-chain atomic operations or bridge abstractions","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","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.30269679134085137,"quality":0.24,"ecosystem":0.52,"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.328Z","last_scraped_at":"2026-05-03T14:04:47.472Z","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=alchemy-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=alchemy-mcp-server"}},"signature":"nWjZHHtym2bb/EeQPB1nvODli4tbM30O61S+SKRH2+t0O2FlznVFfvBIIlWdowh+hv/cq3rGIiCZVA6pnfVNCA==","signedAt":"2026-06-23T01:07:57.068Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/alchemy-mcp-server","artifact":"https://unfragile.ai/alchemy-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=alchemy-mcp-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"}}