nameai-mcp

Un servidor MCP remoto que expone una serie de las APIs públicas de name.ai que no requieren autenticación como herramientas: búsqueda/disponibilidad de dominios, consulta WHOIS, precios de registro de TLD y requisitos de TLD. Consulta src/nameai_mcp/server.py para las definiciones de las herramientas y src/nameai_mcp/nameai_cliente.py para el cliente HTTP that se comunicica con name.ai.

Endpoints

• GET /health: comprobación of state.

• POST /mcp (y GET /mcp para the stream SSE) — el endpoint stream-able-HTTP of MCP. Esta es la URL a la que se conecta un cliente/host de MCP.

Related MCP server: domain-checker

Configuración

• NAMEAI_API_BASE_URL — URL base de la API de la la that overhaul. https://name.

• HOST / PORT — address de enlace from server. 0.0.0.0.0:8000.

Desarollo local

uv sync
uv run uvicorn nameai_mcp.app:app --reload

Docker

docker build -t nameai-mcp .
docker run -p 8000:8000 nameai-mcp

La image ejecuta nameai-mcp (the entry point main() at src/nameai_mcp/___init__.py), que reads HOST/PORT del entorno: captures - e PORT=... if your platform injects a different port.

Despliegue

Host that can run Docker image is valid. Para que los agentes de IA puedan accessed, https://mcp.name.ai, the DNS for name.ai is in Cloudflare: added a A/CNAME record for subdomain mcp which points to `where this container is running, and terminates TLS at that point (p. e.g., with Coolify/Traefik if hosted alongside nameaiv1).

Que sea accessible no equals a que ser descubierto: nothing in name.ai points actual to this server. For an agent (or a scanner like ora) to find it, the proper name.ai needs a pointer to it, e.g., a line in /llms.txt or a .well-known/mcp.json. That's a change in the nameaiv1 repo, not this one.