MCP Server Demo

Created By
josheleonarda year ago
An MCP server for Ethereum Name Service resolutions
Overview

what is MCP Server Demo?

MCP Server Demo is a Model Context Protocol (MCP) server implementation that provides Ethereum Name Service (ENS) lookup functionality, allowing users to resolve Ethereum addresses to ENS names and vice versa.

how to use MCP Server Demo?

To use the MCP Server Demo, install the dependencies, build the server, and start it. The server will run on port 8080, and you can access its API endpoints for ENS lookups.

key features of MCP Server Demo?

  • ENS name resolution (address → name)
  • ENS address lookup (name → address)
  • Server-Sent Events (SSE) for real-time communication
  • Express.js HTTP server

use cases of MCP Server Demo?

  1. Resolving Ethereum addresses to ENS names for user-friendly identification.
  2. Looking up Ethereum addresses from ENS names for transactions.
  3. Real-time communication for ENS updates using SSE.

FAQ from MCP Server Demo?

  • What is ENS?

ENS stands for Ethereum Name Service, which is a distributed, open, and extensible naming system based on the Ethereum blockchain.

  • How do I resolve an ENS name?

You can use the get-ens-address tool by providing an ENS name to get the corresponding Ethereum address.

  • Is the MCP Server Demo free to use?

Yes! The MCP Server Demo is open-source and free to use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
josheleonard
Star
0
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)

a day ago
Crevio

2 days ago