
Ens Mcp
io.github.junct-botPublished by GitHub account junct-botv1.1.0Updated Oct 24, 2026
Ens - 23 tools for name resolution and reverse lookups
Overview
Hosted MCP server exposing 23 Ens tools for name resolution and reverse lookups, with no authentication required.
- What you can do
- Resolve Ens names to their underlying records
- Perform reverse lookups from addresses back to names
- Work with the full set of 23 Ens endpoints, each mapped one-to-one to a real API operation
- When to use it
- Useful when an assistant needs to resolve Ens names or look up the name behind an address, without building your own integration. It is a hosted, free endpoint, so it suits quick experiments and agent workflows that touch Ens naming.
- Requirements
- A remote Streamable HTTP endpoint at ens.mcp.junct.dev/mcp added to the MCP client configuration; no API key, account or local runtime is needed. Network access to the host is required.
Installation
In SourceWeft
- Open Ens Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.junct-bot%2Fens-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"ens": {
"type": "http",
"url": "https://ens.mcp.junct.dev/mcp"
}
}
}README
Ens MCP Server
MCP server for Ens. Agent-ready API for Ens.
Hosted at ens.mcp.junct.dev/mcp. Free to use. No auth. No API key required.
Part of Junct — the agent-readiness layer for the crypto stack.
Quick Start
Add to your MCP client config (Claude Desktop, Cursor, Windsurf):
About
This MCP server is deterministically generated from the Ens API specification. Every tool maps 1:1 to a real API endpoint — no hallucinated endpoints, no phantom tools.
- Protocol: Ens
- Endpoint:
https://ens.mcp.junct.dev/mcp - Transport: Streamable HTTP
- Auth: None required
- Documentation: ens.mcp.junct.dev/llms.txt
- Server card: ens.mcp.junct.dev/.well-known/mcp/server.json
Links
Keywords
Ens, MCP server, DeFi, AI agent, agent-ready API, crypto tools, Model Context Protocol, hosted MCP
Source: README.md at commit 5bb02bb
Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.