Ens Mcp
Resolve ENS names and reverse lookups from your coding agent when building Web3 login, payment, or identity features.
Overview
io.github.junct-bot/ens-mcp is a MCP server for the Build phase that provides twenty-three tools for ENS name resolution and reverse lookups.
What is this MCP server?
- Twenty-three MCP tools for ENS name resolution and reverse lookups
- Hosted streamable-HTTP endpoint at ens.mcp.junct.dev
- Speeds agent-assisted Web3 UX work—profiles, send-to-ENS flows, address labels
- Version 1.1.0 server with GitHub source junct-bot/ens-mcp
- Developer-tools positioning: naming layer for Ethereum apps, not a wallet product
- 23 MCP tools for resolution and reverse lookups
- Server version 1.1.0
- Remote URL: https://ens.mcp.junct.dev/mcp
What problem does it solve?
Web3 features stall when every ENS check forces you to context-switch to explorers or hand-written RPC calls in the agent chat.
Who is it for?
Indie builders adding ENS-powered labels, login hints, or support tooling who want lookup automation inside MCP-aware agents.
Skip if: Teams that need registrar operations, DNS hybrid management, or authoritative on-chain proof without independent verification in production.
What do I get? / Deliverables
After registering the ENS MCP remote, your agent can resolve and reverse-resolve names while you implement identity and payment flows.
- Twenty-three ENS lookup tools callable by your agent
- Faster implementation of name-to-address and address-to-name features
- Reduced manual explorer lookups during Web3 integration coding
Recommended MCP Servers
Journey fit
ENS resolution is a backend and integration concern when shipping products that display or verify Ethereum names. Integrations is the primary shelf because twenty-three MCP tools wrap name resolution for agent-driven development workflows.
How it compares
ENS resolution MCP with twenty-three lookup tools, not a domain purchase marketplace or smart-contract deploy skill.
Common Questions / FAQ
Who is io.github.junct-bot/ens-mcp for?
Solo Web3 developers and agent users who need forward and reverse ENS lookups inside Claude Code, Cursor, or similar MCP clients.
When should I use io.github.junct-bot/ens-mcp?
Use it while building or reviewing features that display, validate, or search Ethereum names and their linked addresses.
How do I add io.github.junct-bot/ens-mcp to my agent?
Add https://ens.mcp.junct.dev/mcp as a streamable-HTTP MCP remote in your client config, then reload to expose the twenty-three ENS tools.