mcpField
D
domain-radar

domain-radar

Local
github.com/tudadadaBusiness & Marketing0Updated 1w ago

About domain-radar

domain-radar is a local MCP server for domain investors, founders, and AI research agents. It scans keyword matches across TLDs, retrieves registration records, and checks live site activity.

Key features

  1. 01Scans keywords across 1,400+ TLDs
  2. 02Sorts domain registrations by date
  3. 03Retrieves RDAP/WHOIS details
  4. 04Checks live website activity
  5. 05Generates filtered keyword domain searches

Use cases

  1. 01Compare a keyword’s registrations across TLDs
  2. 02Review domain age and registrar details
  3. 03Find domains matching placement or character filters

MCP support

It exposes domain scanning, RDAP/WHOIS lookup, and keyword search tools to MCP clients. It runs locally over stdio and requires no API key.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"surf-insight-domain-radar": {
"command": "npx",
"args": [
"-y",
"domain-radar"
]
}
}
}
Run commandnpx -y domain-radar

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmdomain-radar1.2.0

Tools

4

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
excludestringNoSubstring or word to exclude from generated candidates
keywordstringYesThe core keyword to search/audit (e.g. weddingshoes, permafrost, agent)
industryenumNoTarget industry dictionary for word pairingsgeneral | tech | energy | finance | arctic | security
positionenumNoKeyword position: 'beginning' (starts with keyword), 'end' (ends with keyword), or 'any' (keyword anywhere)beginning | end | any
extensionsarrayNoList of TLD extensions to check (e.g. ['com', 'net', 'ai', 'io', 'xyz']). Defaults to ['com'].
max_lengthintegerNoMaximum character length (excluding extension)
min_lengthintegerNoMinimum character length (excluding extension)
include_digitsbooleanNoInclude numeric digits (0-9, 24, 365, etc.). When false, enforces pure letter-only domains.
include_hyphensbooleanNoInclude hyphenated domain variants. When false, enforces strictly unhyphenated domains.
include_alphabetsbooleanNoInclude word/alphabet combinations. Set to false if searching purely numeric variants.
site_status_filterarrayNoFilter returned results by site status: 'active' (live site in use), 'parked' (for sale/parking), 'inactive' (dormant/no DNS), 'unregistered' (available in registry), or 'all'

Details

From the project README

domain-radar

npm version Powered by insight.surf License: MIT

Domain Radar is a production-grade Model Context Protocol (MCP) server powered by insight.surf. Built for domain investors, founders, and autonomous AI research agents, it performs authoritative multi-TLD RDAP registry auditing, historical timeline sorting, keyword combination generation, and real-time live website activity probing.

Core Capabilities

  • 1,400+ Global IANA TLD Full-Spectrum Scanning: Audits exact keywords across the entire directory of over 1,400 top-level domains (.com, .net, .org, .ai, .io, .xyz, .tech, .app, .cloud, .co, .de, ccTLDs, and new gTLDs).
  • Registration Year & Historical Timeline Analysis: Extracts authoritative creation dates / registration years from official RDAP registries and socket WHOIS fallbacks.
  • Chronological Sorting (Oldest $\rightarrow$ Newest): Instantly presents the domain registration history from the earliest legacy registration to the newest active brand.
  • Two-Phase High-Speed Pipeline:
    • Phase 1 (DNS Pre-scan): Multi-worker asynchronous DNS query sweeps all 1,400+ extensions in seconds.
    • Phase 2 (RDAP/WHOIS Deep Inspection): Authoritative extraction of creation date, expiry date, and sponsoring registrar.
  • Live Activity Radar: Probes registered domains in real-time via HTTP/HTTPS to classify them into ACTIVE_IN_USE, PARKED_FOR_SALE, or INACTIVE_DORMANT.
  • Autonomous Agent-Ready (readOnlyHint: true): Zero API keys required, running locally via stdio with $0 operational cost.

Tools Included

1. scan_keyword_tlds (TLD Timeline & Coverage Radar)

Audits an exact keyword across all registered TLDs (over 1,400+ extensions), extracts registration year and creation date for each registered domain, and returns all results sorted chronologically from oldest to newest registration year.

Parameters:

  • keyword (string, required): The core keyword to search (e.g. "openai", "anthropic", "crypto").
  • scope (string, optional, default: "all"):
    • "all": All 1,400+ IANA top-level domains.
    • "popular": Top 80–100 commercial extensions.
    • "gtld": New gTLD extensions.
    • "cctld": 2-letter country-code extensions.
  • sort_by (string, optional, default: "year_asc"):
    • "year_asc": Oldest registration year to newest.
    • "year_desc": Newest to oldest.
    • "alphabetical": Alphabetical by extension.
  • concurrency (integer, optional, default: 40): Parallel DNS worker count.
  • probe_activity (boolean, optional, default: false): Also probe live HTTP/HTTPS status.
2. get_domain_whois

Retrieve detailed RDAP/WHOIS information for any specific domain including creation date, expiry date, registrar, status codes, and live website status.

3. search_keyword_domains

Full DotDB-style domain search engine. Supports keyword placement (beginning, end, any), character filters (include_alphabets, include_digits, include_hyphens), live site status filtering, and custom extension sets.

Installation & MCP Configuration

Add to your MCP configuration file (mcp_config.json or claude_desktop_config.json):

{
  "mcpServers": {
    "domain-radar": {
      "command": "node",
      "args": ["/path/to/domain-radar/index.js"]
    }
  }
}

Or run via npx:

{
  "mcpServers": {
    "domain-radar": {
      "command": "npx",
      "args": ["-y", "domain-radar"]
    }
  }
}

License

MIT © datutu / insight.surf

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.