Domain Check Skills Mcp

io.github.seomarlboroPublished by GitHub account seomarlborov1.2.12Updated Oct 24, 2026

World's fastest domain check. Or the second — dispute it. 50+ TLDs, 6 registrars, no API key.

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

Overview

AI-generated overview

Lets an assistant check domain name availability, compare registrar prices, and look up registration dates across 50+ TLDs.

What you can do
Exposes four tools: check_domain for one domain's availability, premium flags, cheapest registrar, buy link and registration year; search_domains for one name across many TLDs at once; compare_registrars for registration, renewal and three-year totals per registrar; and get_domain_age for a taken domain's registration year and expiration date via RDAP. Availability is resolved through RDAP, DNS-over-HTTPS and registrar APIs, with unresolved names returned as UNKNOWN rather than taken. Pricing comes from a cached registrar price table.
When to use it
Useful when naming a product, project or company and you want the assistant to check candidates, sweep a name across several TLDs, or compare registrar costs without leaving the chat. Also handy for quick registration-date lookups on existing domains.
Requirements
Runs locally over stdio via npx, so Node.js 18+ is needed. No account or API key. Network access to the service's API and public RDAP/DNS endpoints is required. The optional DIGMYNAME_API_BASE environment variable overrides the API base URL.
Before you install
The server sends the domain names you check to a third-party API and its registrar price cache, so treat lookups as external requests. It only reads availability and pricing data; it does not register, buy or modify domains. Buy links point to registrar checkout pages, where any purchase and payment happens outside this server. Rate limited to 60 requests per minute per IP.

Installation

In SourceWeft

  1. Open Domain Check Skills Mcp 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-skills-mcp

[npm version] [downloads] [license]

⚡ The fastest domain availability MCP server — or the second

The fastest domain availability MCP — or the second. A first-time check lands in about half a second (under 0.9 s at p95, measured from the US and the EU, September 2026); a repeat within 60 s is ~0.1 s from the edge cache. Hard-capped so it never hangs. The pipeline (debounce → registry RDAP + DNS → third signal → edge cache) is published openly. Found something faster? Dispute it.

MCP server to check domain availability from any LLM — Claude, Cursor, Windsurf, Continue, Zed. 6 registrars, 50+ TLDs. Powered by DigMyName.

Typical latencyabout half a second first-time check (p50 0.4–0.5 s, under 0.9 s at p95) · ~0.1 s cache-warm — everyday numbers measured from the US and the EU in September 2026, not a lab result; the on-screen timer is the live proof
MethodPublished at digmyname.com/speed
Coverage6 registrars · 50+ TLDs
CostFree — no API key, no account

[domain-check-skills-mcp in action]

Install

Claude Code — one line:

bash
claude mcp add domain-check -- npx -y domain-check-skills-mcp

Claude Desktop / Cursor / Windsurf — add to your MCP config:

json
{  "mcpServers": {    "domain-check": {      "command": "npx",      "args": ["-y", "domain-check-skills-mcp"]    }  }}

Continue (~/.continue/config.json):

json
{  "experimental": {    "modelContextProtocolServers": [      { "transport": { "type": "stdio", "command": "npx", "args": ["-y", "domain-check-skills-mcp"] } }    ]  }}

Zed (settings.json):

json
{  "context_servers": {    "domain-check": {      "command": { "path": "npx", "args": ["-y", "domain-check-skills-mcp"] }    }  }}

VS Code (.vscode/mcp.json):

json
{  "servers": {    "domain-check": { "type": "stdio", "command": "npx", "args": ["-y", "domain-check-skills-mcp"] }  }}

No API key, no account, no config — it works right after install.

Tools

ToolDescription
check_domainAvailability, premium / likely-premium flags, cheapest registrar, direct buy link and registration year (when taken) for one domain.
search_domainsOne name across many TLDs at once (defaults to a curated set of 11). Includes availability, price, buy link and registration year for taken results.
compare_registrarsRegistration, renewal and 3-year totals per registrar for a TLD.
get_domain_ageRegistration year and expiration date for a taken domain via RDAP.

Example prompts

  • "Is acme.io available and where is it cheapest?"
  • "Check nebula across com, io, ai, dev and app."
  • "Compare registrar prices for .ai."
  • "When was stripe.com registered?"

Example response

check_domain for acmeforge.io returns:

acmeforge.io — AVAILABLE  cheapest: Porkbun $28.12/yr  buy: https://porkbun.com/checkout/search?q=acmeforge.io  compare: https://digmyname.com/?q=acmeforge&utm_source=mcp&utm_medium=api&utm_campaign=domain-check-skills

How it works

Availability is resolved through an authoritative-first chain — RDAP (IANA bootstrap), authoritative DNS-over-HTTPS (Cloudflare, Google and AdGuard, hedged), Fastly Domain Research and registrar APIs. Anything unresolved is returned as UNKNOWN rather than falsely reported as taken. Premium candidates are flagged separately so agents never quote a standard retail price for a registry-premium name.

Pricing comes from DigMyName's registrar price cache across 6 registrars and 50+ TLDs.

Domain age is read from registry RDAP endpoints.

Rate limit: 60 requests / minute / IP. Repeat lookups are served from the Cloudflare edge cache in about 0.1 s.

Configuration

Env varDefaultPurpose
DIGMYNAME_API_BASEhttps://api.digmyname.com/functions/v1/public-apiOverride the API base. Set this to the direct Supabase URL to bypass the edge cache.

Releasing (maintainers)

Releases are published from a maintainer's machine:

bash
cd mcp# bump the version in package.json, server.json (two places) and the VERSION constant in src/index.ts; add a CHANGELOG entrynpm run buildnpm publish --provenance=false   # npm asks you to confirm in the browser (web-based 2FA)

The Publish MCP to npm workflow (tag mcp-v*) would publish with provenance from CI, but it needs an NPM_TOKEN repo secret that is not configured; releases so far have been published without provenance.

Requirements

Node.js 18+

Changelog

See CHANGELOG.md.

License

MIT

Source: mcp/README.md at commit 0728846

Tools

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

Version history

2
  1. v1.2.12LatestSep 16, 2026
  2. v1.2.2Sep 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