MCP
Domain availability checks, registrar price comparison and domain age lookups across many TLDs.
Install
The installation steps are in the documentation below. Documentation
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
domain-check-skills-mcp
⚡ 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 latency | about 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 |
| Method | Published at digmyname.com/speed |
| Coverage | 6 registrars · 50+ TLDs |
| Cost | Free — no API key, no account |
Install
Claude Code — one line:
claude mcp add domain-check -- npx -y domain-check-skills-mcp
Claude Desktop / Cursor / Windsurf — add to your MCP config:
{
"mcpServers": {
"domain-check": {
"command": "npx",
"args": ["-y", "domain-check-skills-mcp"]
}
}
}
Continue (~/.continue/config.json):
{
"experimental": {
"modelContextProtocolServers": [
{ "transport": { "type": "stdio", "command": "npx", "args": ["-y", "domain-check-skills-mcp"] } }
]
}
}
Zed (settings.json):
{
"context_servers": {
"domain-check": {
"command": { "path": "npx", "args": ["-y", "domain-check-skills-mcp"] }
}
}
}
VS Code (.vscode/mcp.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
| Tool | Description |
|---|---|
check_domain | Availability, premium / likely-premium flags, cheapest registrar, direct buy link and registration year (when taken) for one domain. |
search_domains | One 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_registrars | Registration, renewal and 3-year totals per registrar for a TLD. |
get_domain_age | Registration year and expiration date for a taken domain via RDAP. |
Example prompts
- "Is
acme.ioavailable and where is it cheapest?" - "Check
nebulaacross com, io, ai, dev and app." - "Compare registrar prices for
.ai." - "When was
stripe.comregistered?"
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 var | Default | Purpose |
|---|---|---|
DIGMYNAME_API_BASE | https://api.digmyname.com/functions/v1/public-api | Override 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:
cd mcp
# bump the version in package.json, server.json (two places) and the VERSION constant in src/index.ts; add a CHANGELOG entry
npm run build
npm 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
Frequently asked questions
What is MCP?
Domain availability checks, registrar price comparison and domain age lookups across many TLDs.
How do I install MCP?
Follow the installation steps in its documentation, shown on this page and in its repository.
Is MCP open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains MCP?
It is published by Seomarlboro. AI.tn lists it but does not maintain or endorse it.
From the community awesome-mcp-servers lists and the project's GitHub repository. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.