DomainKits MCP Server

by abtdomain Your server? Claim it

answering

DomainKits is answering right now. Last checked 4 min ago. 109 installs a week from npm. It exposes 32 tools. Last commit 25 Aug 2026.

Search newly registered, expired, aged, active, deleted and for-sale domains, plus WHOIS and DNS.

Installs per day peak 180 · avg 36 · -12% w/w

a month agotoday

Uptime history 48 days of history

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

218 ms

Response time

average over 24h

109

Installs / week

npm and PyPI

What changed 39

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 August 2026. No other catalogue keeps this.

3 Sep 4 tools changed the parameters they ask for aged, deleted, expired and 1 more

3 Sep a tool description was rewritten expired

28 Aug 6 tools changed the parameters they ask for active, aged, deleted and 3 more

22 Aug 3 tool descriptions were rewritten monitor, nrds, nrds_live

22 Aug a tool changed the parameters it asks for monitor

21 Aug 3 tools appeared epp_status, ip_lookup, registrar

21 Aug 2 tools changed the parameters they ask for nrds, tld_trends

21 Aug a tool description was rewritten nrds

19 Aug 2 tools changed the parameters they ask for domain_changes, tld_trends

19 Aug a tool appeared nrds_live

and 15 more, back to 13 August 2026

What the code does

We read the source, 2 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Package points at a different repository abtdomain/domainkits-mcp

пакет @domainkits/mcp ссылается на abtdomain/domainkits-mcp-js

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add domainkits-mcp --transport http https://api.domainkits.com/v1/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "domainkits-mcp": {
      "url": "https://api.domainkits.com/v1/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.domainkits-mcp]
url = "https://api.domainkits.com/v1/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "domainkits-mcp": {
      "url": "https://api.domainkits.com/v1/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "domainkits-mcp": {
      "url": "https://api.domainkits.com/v1/mcp"
    }
  }
}

This one needs environment variables set before it will start: DOMAINKITS_API_KEY (Optional API key. Without it the server runs on the guest quota.). The author declared them in the registry entry; get the values from the project itself.

Available tools 32

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

tld

tld_check

Check how a prefix is registered across core TLDs, returning per-TLD status and aggregate counts. Related: bulk_tld, available.

tld_rank

Rank TLDs by registration volume and related metrics over a chosen period. Related: tld_trends.

tld_trends

Return registration trend data for a TLD over time, or compare multiple TLDs, in active-total or newly-registered mode. Related: tld_rank, keywords_trends.

bulk

bulk_available

Return the upstream Availability service's point-in-time status for up to 50 domains. available is an affirmative registrability result; registered is already registered; expiring is in an expiry-related lifecycle and is not directly registrable; reserved is registry-reserved; unknown means no verification path produced a reliable conclusion. MCP does not infer availability from failures and removes affiliate fields from the upstream response.

bulk_tld

Check registration status of one keyword across many TLDs at once, returning which TLDs are taken, available, or listed for sale. Related: tld_check, available.

market

market

Search currently registered domains that carry marketplace listing data, filtered by keyword, TLD, listing status, length, and character set. Results are live domains owned by someone. Related: keyword_data, tld_check.

market_price

Check Sedo aftermarket listing price for a domain. Returns status (for_sale, make_offer, or not_found) and listing price when available. Data source is Sedo only; other marketplaces (Afternic, Dan, etc.) are not covered. Related: available, aged.

nrds

nrds

Search newly registered domains from the last 60 days by keyword, or browse a single TLD without a keyword. Filter by recency, registration term, length, character set, and sale status; returns the cross-TLD count for each name. New registrations are folded in continuously, typically 15 to 20 minutes after registration. Two coverage limits worth knowing: dates here are day-level, not clock times, and the 60-day history is gTLD-based, so country-code TLDs such as .ai and .io are present only for the last few days. When you need the exact registration time, the name split into words, or full country-code coverage, use nrds_live, which holds the last three days. Related tools: nrds_live, whois, dns, ns_reverse, typosquat

nrds_live

Search domains registered in the last three days from a live feed covering all TLDs, including country-code ones such as .ai and .io. Returns exact registration and expiry timestamps plus the name split into words; names usually appear within minutes of registration. Use nrds instead for history beyond three days, for registration-term or for-sale filters, for the cross-TLD count, or for deeper paging. nrds carries most of the same recent names, but with day-level dates and a 60-day history that is gTLD-based. Related tools: nrds, whois, dns, typosquat

active

active

Search active gTLD domains from a database of ~240 million registered domains, filtered by keyword, TLD, length, and character set. A market-analysis instrument for keyword distribution and saturation; results are registered domains, not available for registration. Related: expired, whois, dns.

aged

aged

Search currently registered domains with 5-20+ years of history, filtered by keyword, TLD, age range, length, and sale status. These are live domains owned by someone, not free to register. Related: expired, whois, dns.

available

available

Confirm a single domain's registrability and price. The definitive availability check for one domain. Related: bulk_available, whois, monitor.

backlink

backlink_summary

Return a domain's backlink profile: domain rank, total backlinks, referring domains, spam score, and link distribution. Related: whois, safety.

deleted

deleted

Search domains that have completed the deletion cycle and are open for immediate registration at standard cost, filtered by keyword, TLD, age range, length, and character set. Related: available, bulk_available, whois.

dns

dns

Resolve a domain's DNS records, including nameservers and hosting-related records. Related: whois, ns_reverse.

domain

domain_changes

List registration and status changes to premium .com domains (short 1-4 letter and high-value single-word names) over a rolling 7-day window, filtered by change reason and length. Related: whois, ns_reverse.

epp

epp_status

Explain domain EPP status codes: what a code means, why it is set, how serious it is, and what the holder can do. Matches on the code, its aliases, or a category name; call with no query to list every code. Use this to interpret the status field returned by whois instead of relying on recall. Related: whois, expired, monitor.

expired

expired

Search domains in the deletion cycle: expired, in redemption, or pending delete. Still held by the current registrant, with time-sensitive acquisition windows. Filter by lifecycle status, TLD, age range, length, and character set. Note: registrars may renew a domain after it expires, and expiry information here is gathered through multiple channels, so some domain statuses may not match live WHOIS. Related: monitor, deleted, whois.

keyword

keyword_data

Return search-volume, CPC, and competition data for a keyword. Related: keywords_trends.

keywords

keywords_trends

Return provider-computed keyword registration statistics. hot and emerging cover rolling keyword cohorts; prefix returns prefix activity buckets. scope=all represents the provider's filtered all-gTLD sample, while scope=com represents its pure-letter .com subset and is not available for prefix. Results are representative samples, not a complete registry feed, demand measurement, valuation, or investment recommendation.

lookup

ip_lookup

Resolve an IP address or domain name to its network operator and approximate location: ASN, organization, country, region, city, coordinates, and timezone. Domains are resolved to their first IPv4 address before lookup. Location is IP-level and approximate; it is not the address of the site owner. Related: dns, whois, ns_reverse.

monitor

monitor

Manage cross-platform domain monitoring tasks that track changes in WHOIS, DNS, and host-supplied page content. Data is encrypted at rest (AES-256-GCM) in a private per-user directory. Actions: - get: retrieve monitors and check eligible WHOIS/DNS targets, returning current and previous data with change flags. - set: create a monitor, subject to the account tier's maximum. - update: save host-supplied page, WHOIS, or DNS state for a monitor. - delete: remove a monitor. - history: list the changes actually observed over time, optionally for one domain. get compares against the previous check only; history answers when a domain changed and what it changed from. Requires a registered account with memory enabled.

preferences

preferences

Manage user preferences and memory settings. Data is encrypted at rest (AES-256-GCM) in isolated per-user directories. Actions: - get: report whether memory is enabled and return saved preferences. - set: save preferences; memory_enabled must be true before any preferences, monitors, or strategies can be stored, and requires explicit user consent. - delete: permanently erase all stored user data (GDPR Article 17). Related: monitor, strategy.

price

price

Return standard registration and renewal price for a TLD. Related: available.

registrar

registrar

Look up ICANN-accredited registrars by name, alias, or IANA ID. Returns accreditation status, RDAP endpoint, business contact details, a drop-catch flag, and the parent entity for reseller shells. Around 60 percent of accredited registrars are shells operated by a handful of parents, so parent_id is what tells you who actually runs a name. Related: whois, available, expired.

reverse

ns_reverse

Reverse NS lookup: find all gTLD domains hosted on a specific nameserver, filtered by TLD and keyword. Related: whois, dns.

safety

safety

Return Google Safe Browsing status for a domain. Related: whois, backlink_summary.

strategy

strategy

Store user-authored strategy text, execution timestamps, and the most recent result in encrypted per-user storage. This tool does not provide presets, define opportunities, choose domains, or execute a workflow. Requires a registered account with memory enabled.

typosquat

typosquat

Generate typosquat permutations for a domain and check which variants are registered. Produces omission, transposition, keyboard-adjacent replacement, insertion, repetition, hyphenation, vowel-swap, homoglyph, plural/singular, and TLD-swap variants. Each result includes the variant domain, mutation type, prefix TLD count (how many TLDs the prefix is registered under), and registration date if known. Use for brand protection, phishing detection, and defensive registration planning. Related tools: nrds, ns_reverse, dns, whois, safety.

unregistered

unregistered_ai

Search unregistered short .ai domains by pattern (CVCV, CVCC, and other 3-4 letter shapes) that are still available for registration. Related: available, bulk_available.

usage

usage

Return the current account tier, per-tool-group usage, rate limits, and stateful Monitor and Strategy quotas.

whois

whois

Return WHOIS/RDAP registration data for a domain: registrar, dates, status, and nameservers. Related: dns, safety.

Endpoints

URL	Transport	State	Latency	Checked
https://api.domainkits.com/v1/mcp	streamable-http	answering	173 ms	4 min ago

Alternatives to DomainKits

same job, measured the same way

Midnight Rgb

by midnight-rgb

Domain registrar for AI agents. Search, register, and manage domains via API.

24 installs/wk local only

Customdomain

by customdomain

Custom domains for SaaS and AI agents: search, register, connect DNS, and issue HTTPS over MCP.

answering

EnCirca Domains

by encirca

Search, Register , Renew , Transfer and Manage domains

10 tools answering

Bloomfilter

by eronmmer

Service that lets AI Agents search, register, and configure domains

90 installs/wk local only

Dynadot

by mikusnuz

MCP server for Dynadot domain registrar — domain search, registration, DNS, and transfers

60 installs/wk local only

Agentdomain MCP

by agentdomain

138 installs/wk local only

Agent Domain Search

by agentdomainsearch

Agent-first domain registration and DNS management, paid with USDC via x402.

3 tools answering

Nimrod Research

by orchis

Web research for agents: quality-scored Google search, webpage extraction, and deep research.

answering

DomainKits — questions

Answers built from our own checks of this server.

What can DomainKits do?

It exposes 32 tools, read directly from the server on our last check. Among them: active, aged, available, backlink_summary, bulk_available, bulk_tld and 26 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is DomainKits mostly used for?

Its tools cluster around tld, nrds and bulk. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is DomainKits working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 218 ms. The bar chart above shows every period we have measured.

How do I connect DomainKits?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does DomainKits need an API key?

No. DomainKits completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 32 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is DomainKits?

It answers our handshake in 218 ms on average, which is faster than 64% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use DomainKits?

The npm package @domainkits/mcp was installed 109 times in the last week. Week over week that is -12%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is DomainKits open source?

Yes — it is published under the MIT licence, 6 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.