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.