Domain Check

io.github.stucchiPublished by GitHub account stucchiv1.1.1Updated Oct 24, 2026

Check domain availability across 500+ TLDs. Single and bulk checks with UI.

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant check whether a domain name is available for registration across 500+ TLDs.

What you can do
Check a single domain name for availability and registration status, with the result returned as structured data (domain, available, status). Lookups are routed by TLD: RDAP over HTTP for 500+ gTLDs and ccTLDs, with WHOIS fallback for TLDs such as .de and .cn.
When to use it
Useful when naming a project, product or brand and you want the assistant to test candidate domain names for availability without leaving the conversation.
Requirements
Runs locally as a Python package (domain-check-mcp) launched via uvx, so a Python environment with uv/uvx is needed. No accounts, API keys or environment variables are declared. Outbound network access is required for RDAP HTTP lookups and WHOIS TCP port 43 queries.
Before you install
Each check sends the queried domain name to public RDAP or WHOIS services of the relevant registry, so candidate names are visible to third parties. Results reflect registry data at query time and are not a reservation; availability can change before registration.

Installation

In SourceWeft

  1. Open Domain Check in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

domain-check-mcp

[PyPI] [License: MIT] [Python] [MCP Server] [MCP Enabled] [Claude Compatible] [GitHub stars] [GitHub issues]

MCP server for checking domain name availability. Supports 500+ TLDs via RDAP, with WHOIS fallback for .de and .cn.

Installation

bash
uvx domain-check-mcp

Usage in .mcp.json

json
{  "mcpServers": {    "domain-check": {      "command": "uvx",      "args": ["domain-check-mcp"]    }  }}

Tools

  • check_domain — Check if a domain name is available for registration

Example

check_domain("example.com")

Returns:

json
{  "domain": "example.com",  "available": false,  "status": "registered"}

Supported TLDs

Via RDAP (500+)

All major gTLDs and many ccTLDs with RDAP support, sourced from the IANA RDAP Bootstrap:

.com, .net, .org, .info, .app, .dev, .io, .xyz, .site, .shop, .uk, .fr, .nl, .pl, .consulting, .cloud, .tech, .blog, .store, .online, and many more.

Via WHOIS

TLDWHOIS Server
.dewhois.denic.de
.cnwhois.cnnic.cn
.fjwww.whois.fj
.gswhois.nic.gs
.bayernwhois.nic.bayern
.catwhois.nic.cat
.euswhois.nic.eus
.radiowhois.nic.radio
.scotwhois.nic.scot
.sportwhois.nic.sport

How it works

  1. Extracts the TLD from the domain name
  2. Routes to the appropriate adapter (RDAP or WHOIS)
  3. RDAP: HTTP lookup — 404 means available, 200 means registered
  4. WHOIS: TCP port 43 lookup — pattern matching on the response
  5. Returns a structured result with availability status

Development

bash
git clone https://github.com/stucchi/domain-check-mcp.gitcd domain-check-mcppython -m venv .venvsource .venv/bin/activatepip install -e ".[dev]"pytest

License

MIT

Source: README.md at commit 04b0151

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Check integrations