Marketing

namebuddy.ai

Checks domain name availability and builds links to an AI name generator for brand or product naming.

1 endpoint2 known toolsFirst detected September 15, 2026Last detected September 15, 2026

ENDPOINT 1

https://namebuddy.ai/api/mcp

No auth detected

MCP server metadata

Name: namebuddy
Version: 1.0.0

Capabilities

tools

Server instructions

Use check_domains to verify whether specific domain names are registrable — the answer comes from the registry's own record, not a reseller. Use build_generator_link when the user wants brandable name ideas rather than a check on names they already have.

Known tools 2

check_domains

Check whether one or more domain names are available to register.

Inferred read-only

build_generator_link

Build a namebuddy.ai link that opens the AI name generator prefilled with a brief, so a person can run it.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.namebuddy]
url = "https://namebuddy.ai/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "namebuddy": {
      "type": "http",
      "url": "https://namebuddy.ai/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: namebuddy
Remote MCP URL: https://namebuddy.ai/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "namebuddy": {
      "url": "https://namebuddy.ai/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "namebuddy": {
      "type": "http",
      "url": "https://namebuddy.ai/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "namebuddy",
  "transport": "streamable-http",
  "url": "https://namebuddy.ai/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.