Give your agent a domain registrar
Every Namefi API operation as a typed tool. Connect once and your agent works with real domains, real DNS, real money.
- 50 tools
- generated from the API, so they never drift from the product
- Streamable HTTP
- the current MCP transport, SSE included
- API key or OAuth
- every request is authenticated
One protocol instead of one integration per app
An open standard for connecting AI apps to real systems. One protocol, and every server that speaks it becomes available.
Write the integration once
Typed tools, not screen scraping
A real permission boundary
The whole registrar, as tools
Namefi is an ICANN-accredited registrar. These tools are generated from the same API that powers the app.
Search and availability
Registration and payment
DNS records
Portfolio and orders
Balance and funding
Wallet identity
Two minutes to your first tool call
Add the server, authenticate, ask for something. Any MCP client works.
claude mcp add --transport http namefi https://api.namefi.io/mcp \
--header "X-API-Key: <your-api-key>"Configure https://api.namefi.io/mcp. The apex https://namefi.io/mcp also answers MCP traffic, but only for API-key callers.
One install, server and skill together
Namefi ships first-party plugins for Claude Code, Codex, and ZCode. Each bundles the MCP server and a skill that teaches the agent how to use it.
/plugin marketplace add d3servelabs/namefi-claude-plugins
/plugin install namefi@namefiRun both commands in Claude Code. Then open /mcp, pick plugin:namefi:api, and sign in — the tools appear once you do.
Two ways in, no anonymous access
Every request is authenticated, including read-only ones. Pick what fits how your agent runs.
API key
OAuth 2.1
There is no anonymous tier — an agent's access always traces to a credential you control.
Listed, indexed, and discoverable
A server is only useful if a client can find it.
Public registry
Official MCP Registry
io.namefi/mcpThe upstream index other catalogs build on, and the only listing tied cryptographically to namefi.io.
Glama
io.namefi/mcpAn independent directory, so developers meet Namefi while comparing servers.
Smithery
d3serve/namefiInstalls straight into a client, shortening discovery to a first tool call.
Discovery from namefi.io
Server descriptor
/.well-known/mcp/servers.jsonServed from namefi.io itself, so the domain vouches for the endpoint.
Agent instructions
/llms.txtOften the first thing an agent reads, pointing it at the server before scraping starts.
Verified by DNS
Proven with an ed25519 key in DNS, mirrored at /.well-known/mcp-registry-auth.
Point an agent at it
Bring your client, or start with an API key and one availability check.