Domain Check Skills Mcp

io.github.seomarlboro由 GitHub 帳號 seomarlboro 發布v1.2.12更新於 Oct 24, 2026

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

發布方自己的服務：check.tattoo: tattoo size and placement guide

已驗證STDIO僅桌面網頁搜尋與抓取商業與電商

服務詳細資訊

識別碼: io.github.seomarlboro/domain-check-skills-mcp
傳輸: STDIO
執行環境: Desktop only
信任: Verified
發布於: Sep 16, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 seomarlboro。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.seomarlboro%2Fdomain-check-skills-mcp.svg)](https://sourceweft.com/mcp/io.github.seomarlboro%2Fdomain-check-skills-mcp?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

讓助理查詢網域名稱是否可註冊、比較註冊商價格，並查詢 50 多個頂級網域的註冊時間。

可以做什麼: 提供四個工具：check_domain 查詢單一網域的可用性、溢價標記、最便宜註冊商、購買連結和註冊年份；search_domains 一次把一個名稱在多個頂級網域上批次查詢；compare_registrars 比較各註冊商的註冊、續約和三年總價；get_domain_age 透過 RDAP 查詢已註冊網域的註冊年份和到期日。可用性透過 RDAP、DNS-over-HTTPS 和註冊商介面解析，無法確認的名稱會回傳 UNKNOWN，而不是誤報為已註冊。價格來自快取的註冊商價格表。
適用情境: 適合為產品、專案或公司命名時，讓助理檢查候選網域、把一個名稱在多個頂級網域上掃一遍，或在不離開對話的情況下比較註冊商費用。也適合快速查詢既有網域的註冊日期。
執行需求: 透過 npx 以 stdio 方式在本機執行，需要 Node.js 18+。不需要帳號或 API 金鑰。需要能連線到該服務的 API 以及公開的 RDAP/DNS 端點。選用環境變數 DIGMYNAME_API_BASE 可覆寫 API 基礎網址。

安裝前請注意

此伺服器會把您查詢的網域傳送到第三方 API 及其註冊商價格快取，應視為對外請求。它只讀取可用性和價格資料，不會註冊、購買或修改網域。購買連結指向註冊商的結帳頁面，任何購買與付款都在此伺服器之外進行。速率限制為每個 IP 每分鐘 60 次請求。

安裝

在 SourceWeft 中

開啟儀表板中的 Domain Check Skills Mcp，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照儲存庫中的啟動說明。

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 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

[domain-check-skills-mcp in action]

Install

Claude Code — one line:

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

json

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

{  "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"] } }    ]  }}

{  "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"] }    }  }}

{  "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"] }  }}

{  "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.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

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

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)

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.