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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago