NNS-MCP

Created By
nadnameservicea year ago
Nad Name Service MCP Server
Overview

what is NNS-MCP?

NNS-MCP (Nad Name Service - Model Context Protocol) is a server designed to interact with the Nad Name Service (NNS), a Web3 name service built on the Monad blockchain.

how to use NNS-MCP?

To use NNS-MCP, clone the repository from GitHub, install the necessary dependencies using npm or yarn, and run the development server to access its tools.

key features of NNS-MCP?

  • Get the resolved address of a .nad name.
  • Retrieve profile information of a wallet address.
  • Transfer MON to a specified wallet address.

use cases of NNS-MCP?

  1. Resolving .nad names to their corresponding addresses.
  2. Accessing wallet profile information for user verification.
  3. Facilitating transactions by transferring MON between wallet addresses.

FAQ from NNS-MCP?

  • What are the prerequisites for using NNS-MCP?

You need Node.js (version 14 or higher) and npm or yarn to install dependencies.

  • How do I contribute to NNS-MCP?

You can contribute by forking the repository, creating a new branch, and submitting a pull request with your changes.

  • Is there a license for NNS-MCP?

Yes, this project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nadnameservice
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