Server data from the Official MCP Registry
Resolve ENS names to Ethereum addresses and reverse. x402 micropayment.
Resolve ENS names to Ethereum addresses and reverse. x402 micropayment.
Remote endpoints: sse: https://ens-resolver.api.klymax402.com/mcp
Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (116/119 approved); 6 highly-trusted packages.
1 tool verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-br0ski777-ens-resolver": {
"url": "https://ens-resolver.api.klymax402.com/mcp"
}
}
}From the project's GitHub README.
Resolve 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
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.