API Tools

domainlookup.dev

Checks domain availability, suggests TLD alternatives, and retrieves WHOIS/RDAP registration and expiration data.

1 endpoint7 known toolsFirst detected October 22, 2026Last detected October 22, 2026

ENDPOINT 1

https://domainlookup.dev/mcp

No auth detected

MCP server metadata

Name: domainlookup
Version: 1.0.0

Capabilities

tools

Server instructions

Domain Lookup (domainlookup.dev), free domain research tools backed by the registries themselves (RDAP, WHOIS), DNS-over-HTTPS and Certificate Transparency. Availability is only reported as available when the registry confirms it; "unknown" means it could not be verified. Tool calls need a free API key from https://domainlookup.dev/#api-key; without one, relay the key instructions to the user. Use check_domain_availability or suggest_domains for "is X free?", whois_lookup for registrar/expiry, dns_lookup for records, ssl_certificates for certificates and subdomains. Data is live, not cached.

Known tools 7

check_domain_availability

Check whether a domain is available to register.

Inferred read-only

bulk_check_availability

Check availability of up to 10 domains at once.

Inferred read-only

suggest_domains

Check one name across many TLDs (acme → acme.com, acme.io, acme.ai, …) and report which are available.

Inferred read-only

whois_lookup

Registration data from the registry over RDAP (modern WHOIS): registrar, abuse contact, creation/expiry/update dates, EPP status codes, nameservers, DNSSEC, domain age.

Potential side effects

domain_age

How old a domain is (registration date, age in days/years) and how many days until it expires.

Inferred read-only

dns_lookup

DNS records of a name via Cloudflare DNS-over-HTTPS.

Inferred read-only

ssl_certificates

SSL/TLS certificates issued for a domain, from Certificate Transparency logs (crt.sh): issuer, validity, names, plus every hostname seen on them (a quick subdomain inventory).

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.domainlookup]
url = "https://domainlookup.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "domainlookup": {
      "type": "http",
      "url": "https://domainlookup.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: domainlookup
Remote MCP URL: https://domainlookup.dev/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": {
    "domainlookup": {
      "url": "https://domainlookup.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "domainlookup": {
      "type": "http",
      "url": "https://domainlookup.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "domainlookup",
  "transport": "streamable-http",
  "url": "https://domainlookup.dev/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.