ENS MCP Server

Created By
JustaName-ida year ago
Overview

what is ENS MCP Server?

ENS MCP Server is a server designed for the Ethereum Name Service (ENS) that allows users to interact with the ENS system to resolve names, check availability, retrieve records, and more.

how to use ENS MCP Server?

To use the ENS MCP Server, clone the repository, install the dependencies, configure Ethereum providers, and then run the server using either npx or a local script.

key features of ENS MCP Server?

  • Resolve ENS names to Ethereum addresses.
  • Perform reverse lookups to get ENS names from Ethereum addresses.
  • Retrieve text records associated with ENS names.
  • Check the availability of ENS names for registration.
  • Get comprehensive information about ENS names, including ownership and history.
  • Support for subdomain queries and registration price checks.

use cases of ENS MCP Server?

  1. Resolving ENS names for dApps and wallets.
  2. Checking the availability of desired ENS names for new users.
  3. Retrieving metadata associated with ENS names for display in applications.
  4. Managing ENS name registrations and subdomains.

FAQ from ENS MCP Server?

  • What is the purpose of the ENS MCP Server?

The ENS MCP Server facilitates interaction with the Ethereum Name Service, allowing users to resolve names and manage ENS records.

  • How do I install the ENS MCP Server?

You can install it by cloning the repository and running npm install in the project directory.

  • Is there a cost associated with using the ENS MCP Server?

The server itself is free to use, but registering ENS names may incur costs as per Ethereum's pricing.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JustaName-id
Star
3
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

9 hours ago