Best for
- Developers and researchers needing quick EVM address labels
- AI assistants that interact with the Ethereum ecosystem
- Users who want access to public dataset
E
Eth Labels MCP Server
Community
A public dataset of labeled crypto addresses for EVM chains
GitHub source repository ↗
47FMRS · D
The Eth Labels MCP server provides a simple and useful interface for EVM address label lookup. It relies on a public dataset, is easy to install, and supports multiple clients. Suitable for users needing quick label lookups, but note that data may not be real-time.
The Eth Labels MCP server allows AI assistants to look up public labels for Ethereum and other EVM chain addresses and tokens. The dataset includes over 115,000 accounts and 54,000 tokens, totaling more than 170,000 entries, sourced from Etherscan. It provides three tools: address lookup, label search, and dataset statistics. It is available via the npm package eth-labels-mcp, no repository clone needed.
Tools
lookup_address
Look up any Ethereum/EVM address to get its label and name tag
search_labels
Search by project name, label, or token symbol (e.g. 'uniswap', 'binance', 'USDC')
dataset_stats
Get dataset statistics — 115k+ accounts, 54k+ tokens, 170k+ total entries
Setup
- Ensure Node.js 18 or higher is installed.
- Depending on your AI client, follow the setup instructions in the README to add the MCP server. For Claude Code, run:
claude mcp add eth-labels-mcp -- npx -y eth-labels-mcp. For other clients, add a similar JSON configuration to the appropriate config file (usingnpx -y eth-labels-mcp). - Restart the client, then test with a query like: 'Search for "uniswap" addresses'.
claude_desktop_config.json
{
"mcpServers": {
"eth-labels": {
"command": "npx",
"args": [
"-y",
"eth-labels-mcp"
]
}
}
}
Fit and risk
Not for
- Scenarios requiring real-time or dynamic label updates
- Users needing non-public or proprietary address data
- Users requiring advanced analytics or complex queries
Required permissions
- No API key or authentication required
- Only uses public data
- Requires network access to fetch the dataset
Risks and side effects
- Data may be incomplete or inaccurate
- Dataset may not be updated in real-time
- Labels may not reflect the latest state
Troubleshooting
- Ensure Node.js version is 18 or higher
- Check MCP configuration for correct command and args
- If queries return empty, try different search terms or addresses
Use cases
Identify addresses or contracts involved in transactions
Find labels for project-related addresses
Get overall dataset size information
Supported clients
Claude DesktopFull support
Claude CodeFull support
CursorFull support
WindsurfFull support
VS Code (GitHub Copilot)Full support
ClineFull support