This server connects Claude to the Ethereum Name Service, letting you resolve .eth domains to wallet addresses and do reverse lookups from addresses back to names. It runs on the x402 micropayment protocol, so you'll need to handle per-request pricing. Useful when you're building crypto tools or agents that need to translate human-readable ENS names into addresses for transactions or lookups. The implementation is TypeScript based and accessible via SSE transport at a hosted endpoint. Reach for this when you need ENS resolution without spinning up your own Ethereum node or managing API keys for third-party services.
Public tool metadata for what this MCP can expose to an agent.
crypto_resolve_ensUse this when you need to resolve an ENS name to an Ethereum address, or reverse-resolve an address to its ENS name. Returns resolution data in JSON. 1. address: resolved Ethereum address (0x...) 2.2 paramsUse this when you need to resolve an ENS name to an Ethereum address, or reverse-resolve an address to its ENS name. Returns resolution data in JSON. 1. address: resolved Ethereum address (0x...) 2.
namestringaddressstringResolve ENS names to ETH addresses and reverse -- avatar URLs included. Identity layer for agents. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"ens-resolver": {
"url": "https://ens-resolver.api.klymax402.com/mcp"
}
}
}
curl -X POST "https://ens-resolver.api.klymax402.com/api/resolve" \
-H "Content-Type: application/json" \
-d '{}'
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
crypto_resolve_ens | POST | /api/resolve | $0.002 | Resolve ENS name to Ethereum address or reverse-resolve address to ENS name |
crypto_resolve_ensUse this when you need to resolve an ENS name to an Ethereum address, or reverse-resolve an address to its ENS name. Returns resolution data in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
name | string | no | ENS name to resolve (e.g. vitalik.eth) |
address | string | no | Ethereum address for reverse resolution (e.g. 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045) |
Returns
address -- resolved Ethereum address (0x...)ensName -- ENS name (e.g. vitalik.eth)avatar -- avatar URL associated with the ENS name (if set)resolvedDirection -- "forward" (name to address) or "reverse" (address to name)Example response:
{"address":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045","ensName":"vitalik.eth","avatar":"https://...","resolvedDirection":"forward"}
When to use: sending funds to an ENS name to verify the correct address. Essential for identity resolution and human-readable wallet lookup.
Not for: wallet balances (use wallet_get_portfolio), token safety (use token_check_safety), NFT metadata (use crypto_get_nft_metadata).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT
io.github.shelvick/shopify-subscription-reconciliation
zleventer/google-ads-mcp
csoai-org/meok-stripe-acp-checkout-mcp
csoai-org/stripe-billing-mcp
io.github.mharnett/google-ads
co.pipeboard/google-ads-mcp