Loading...

Web3 MCP provides access to Ankr's Advanced API, enabling LLMs to interact with blockchain data across multiple chains for querying and NFT/token information.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
Web3 MCP provides access to Ankr's Advanced API, enabling LLMs to interact with blockchain data across multiple chains for querying and NFT/token information.
Web3 MCP is relatively safe for read-only operations, providing access to blockchain data through Ankr's API. However, the presence of a private key for authenticated requests introduces risk if the key has write permissions or is compromised. Proper configuration and monitoring are essential to mitigate potential risks.
Performance is primarily dependent on the Ankr API's response times and network latency. Consider caching frequently accessed data to improve responsiveness.
Cost is determined by Ankr's API pricing model, which may be based on usage volume or specific API calls. Monitor API usage to avoid unexpected costs.
{
"mcpServers": {
"web3": {
"command": "uvx",
"args": [
"web3-mcp"
],
"env": {
"ANKR_ENDPOINT": "https://rpc.ankr.com/...",
}
}
}
}ANKR_ENDPOINTANKR_PRIVATE_KEYget_nfts_by_ownerRetrieves NFTs owned by a specified wallet address.
Read-only operation; retrieves data without modifying blockchain state.
get_account_balanceFetches the token balances for a given wallet address.
Read-only operation; retrieves data without modifying blockchain state.
get_transactions_by_hashRetrieves transaction details based on its hash.
Read-only operation; retrieves data without modifying blockchain state.
get_nft_metadataRetrieves metadata for a specific NFT.
Read-only operation; retrieves data without modifying blockchain state.
Environment Variable
Web3 MCP is relatively safe for read-only operations, providing access to blockchain data through Ankr's API. However, the presence of a private key for authenticated requests introduces risk if the key has write permissions or is compromised. Proper configuration and monitoring are essential to mitigate potential risks.
Autonomy is limited by the permissions associated with the ANKR_PRIVATE_KEY. If no key is provided, it defaults to read-only. Ensure appropriate key management for desired autonomy level.
Production Tip
Monitor API usage and error rates to proactively identify and address potential issues with the Ankr API or the `web3-mcp` server.
Ethereum, BSC, Polygon, Avalanche, and more. Refer to Ankr's Advanced API documentation for a complete list.
No, it's optional. However, it's recommended for authenticated requests that may require write access.
Implement retry logic with exponential backoff and monitor API usage to stay within rate limits.
Securely store the ANKR_PRIVATE_KEY and ANKR_ENDPOINT, and implement proper input validation to prevent injection attacks.
Implement logging and monitoring to track API usage, error rates, and response times.
Ankr's Advanced API may have a free tier, but check their pricing for current details.
NFT metadata, token balances, transaction history, blockchain statistics, and more. See the API Categories in the README.