Namefi

io.namefiPublished by namefi.ioOfficial publisherv3.0.0Updated Oct 25, 2026

Search, buy, and manage domains, DNS records, orders, and NFSC balance on Namefi.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingCloud & Infrastructure

Overview

AI-generated overview

Namefi's remote MCP server lets an assistant search, buy and manage domains, DNS records and orders, and check NFSC balance on Namefi.

What you can do
Search for and purchase domains through Namefi, including checking availability and placing orders. Manage existing domains and their DNS records. Review orders and account activity. Check the NFSC token balance associated with the account.
When to use it
Useful when you want an assistant to handle domain registration and DNS administration on Namefi directly, for example checking availability, buying a name, or updating records without switching to the web dashboard.
Requirements
A remote MCP endpoint at api.namefi.io over streamable HTTP. Authentication is required: either a Namefi API key sent in the X-API-Key header, created in the Namefi account, or OAuth 2.1 sign-in with authorization code and PKCE plus dynamic client registration. A Namefi account and network access are needed.
Before you install
The server can spend money by buying domains and can change or delete DNS records and orders, so actions should be confirmed before running. It requires an API key or OAuth sign-in, which grants access to the Namefi account; keep the key secret. Domain and account data is sent to Namefi's remote service.

Installation

In SourceWeft

  1. Open Namefi in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.namefi%2Fmcp/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "namefi": {
      "type": "http",
      "url": "https://api.namefi.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v3.0.0LatestSep 16, 2026

Score

67% 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
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.