Name.ai MCP Server

ai.name由 name.ai 发布官方发布者v1.0.1更新于 Oct 24, 2026

Domain availability search, WHOIS lookup, TLD pricing and registry rules from name.ai. Read-only.

已验证Streamable HTTP可网页运行网页搜索与抓取商业与电商

服务详情

标识符: ai.name/nameai-mcp
传输: Streamable HTTP
运行时: Web executable
信任: Verified
发布于: Sep 16, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此服务的命名空间属于 name.ai，且该域名同时运行其端点。这可以确认发布者，但并不代表该服务的工具是安全的。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.name%2Fnameai-mcp.svg)](https://sourceweft.com/mcp/ai.name%2Fnameai-mcp?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

name.ai 提供的远程只读 MCP 服务器，让助手查询域名可用性、WHOIS 记录，以及 TLD 价格和注册规则。

可以做什么: 查询某个域名及其常见其他 TLD 是否可注册，未经 name.ai API 授权时隐藏二级市场一口价（search_domain）。查询 WHOIS/RDAP 注册信息，如注册商、注册人、创建与到期日期、名称服务器（whois_lookup）。获取某 TLD 的新注册、转入、续费或赎回恢复的当前美元价格（tld_registration_price）。获取 TLD 的注册政策：可注册年限范围、是否要求组织、允许的注册人国家及名称服务器规则（tld_requirements）。
适用场景: 适合在调研或挑选域名时，把可用性、归属和价格信息直接带入对话。也适合在注册或转移域名前核对注册局政策。
运行要求: 远程 streamable-http 端点；未声明客户端需要认证、API 密钥或环境变量。服务器自身调用 name.ai 的公开 API，WHOIS 查询按调用方 IP 限制为每天 10 次。

安装前请注意

只读，但 WHOIS 查询共用服务器出口 IP，因此每日限额由该端点的所有使用者共享。未经授权时二级市场一口价会被隐藏。返回的价格是 name.ai 自身的注册价格，而非市场价格。域名查询会发送到 name.ai 的 API。

安装

在 SourceWeft 中

打开控制台中的 Name.ai MCP Server，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/ai.name%2Fnameai-mcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "name-ai": {
      "type": "http",
      "url": "https://mcp.name.ai/mcp"
    }
  }
}

README

nameai-mcp

A remote MCP server exposing a handful of name.ai's public, no-auth-required APIs as tools: domain search/availability, WHOIS lookup, TLD registration pricing, and TLD requirements. See src/nameai_mcp/server.py for the tool definitions and src/nameai_mcp/nameai_client.py for the HTTP client that talks to name.ai.

Endpoints

GET /health — health check.
POST /mcp (and GET /mcp for the SSE stream) — the MCP streamable-http endpoint. This is the URL an MCP client/host connects to.

Configuration

NAMEAI_API_BASE_URL — base URL of the name.ai API this server calls. Defaults to https://name.ai.
HOST / PORT — bind address for the server itself. Default 0.0.0.0:8000.

Local development

Docker

The image runs nameai-mcp (the main() entry point in src/nameai_mcp/__init__.py), which reads HOST/PORT from the environment — pass -e PORT=... if your platform injects a different port.

Deploying

Any host that can run the Docker image works. It is deployed through Coolify on the Hetzner server and served at https://mcp.name.ai/mcp (streamable-http), with Traefik terminating TLS. The original hostname, https://nameai-mcp.h.namekart.com/mcp, still routes to the same container, so client configs written against it keep working.

mcp.name.ai is a DNS-only A record to the Hetzner box. It exists because scanners and MCP tooling look for a server at mcp.<domain> instead of reading the URL out of a manifest — ora's scanner was watched, in this container's own access log, never dialling the manifest's mcpUrl during a scan. Adding a hostname needs two things besides DNS: the domain on the Coolify app, and the host appended to MCP_ALLOWED_HOSTS, without which the SDK's DNS-rebinding guard answers it with 421.

The server calls the public API at NAMEAI_API_BASE_URL, default https://name.ai. Since name.ai moved to Hetzner that resolves to the same host this container runs on, so the calls leave the container, reach the host's own public IP, and come back in through Traefik. That hairpin works here and is left in place deliberately: talking to the API exactly the way an outside client would is the point of this server.

Being reachable isn't the same as being discovered — and that part is done. name.ai advertises this server in four places:

https://name.ai/.well-known/mcp.json — manifest
https://name.ai/.well-known/mcp/server-card.json — server card
https://name.ai/llms.txt — in both the endpoint list and the tool guidance
the MCP Registry, namespace ai.name, domain-verified

All four live in the nameaiv1 repo. If the deployed URL changes, they change with it — otherwise agents keep being pointed at the old one.

来源：README.md，提交 1f6e737

工具

search_domain

Check whether a domain is available and, for the same label, whether its common alternate TLDs are too (e.g. querying "acme.com" also returns "acme.ai", "acme.io", ...). Backed by POST /api/domain/search — public, no auth required. Buy-now (aftermarket/marketplace) prices are hidden unless you're authenticated (see AUTH.md at name.ai for how to get a token) — an unauthenticated call only sees new-registration pricing for a domain that's simply unregistered. Pass a valid OAuth access token as this call's Authorization header and it's forwarded automatically. Args: domain: A domain name to check, e.g. "example.ai". include_alternates: When true (default), also return sibling TLDs for the same label. When false, only the exact domain is returned.

输入参数domain必填include_alternates

whois_lookup

Look up WHOIS/RDAP registration details for a domain: registrar, registrant, creation/expiration dates, nameservers. Backed by POST /api/tools/whois — public, no auth required, but rate limited by name.ai to 10 lookups per day per caller IP. Since every MCP call shares this server's egress IP, that quota is pooled across all of this MCP server's callers, not per end user. Args: domain: A domain name to look up, e.g. "example.com".

输入参数domain必填

tld_registration_price

Get the current USD price for a domain-lifecycle operation on a TLD (new registration, transfer-in, renewal, or restore from redemption). Backed by GET /api/pricing/tld — public, no auth required. This is name.ai's own registration pricing, not an aftermarket/marketplace price, so it is never gated by sign-in status. Args: tld: The TLD without a leading dot, e.g. "ai" or "com". operation: One of "register", "transfer", "renew", "restore".

输入参数tld必填operation

tld_requirements

Get registration requirements for a TLD: allowed registration period range, whether an organization is required, allowed registrant countries, nameserver rules, and similar registry policy. Backed by GET /api/tlds/{tld}/metadata — public, no auth required. Args: tld: The TLD without a leading dot, e.g. "ai" or "io".

输入参数tld必填