Skip to main content
Glama
deenesjakoruzh
imprvhub

Domain Availability Checker MCP

by imprvhub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

MCP 域名可用性检查器

铁匠徽章

特征

  • 域名可用性检查

    • 检查 50 多个热门 TLD 扩展名的可用性

    • 支持流行（.com、.io、.ai）、国家（.us、.uk、.de）和新 TLD（.app、.dev、.tech）

    • 使用 DNS 和 WHOIS 进行双重验证以确保准确性

    • 按受欢迎程度组织的智能 TLD 建议

  • 搜索功能

    • 检查具有精确 TLD 匹配的特定域名

    • 对给定名称支持的扩展进行批量检查

    • 并行处理以实现更快的域查询

    • 按 TLD 类别组织的结果

  • MCP 集成

    • 使用 uvx 包管理轻松设置

    • 与 Claude Desktop 无缝集成

    • 实时可用性状态更新

    • 性能指标和时间信息

  • AI助手功能

    • 通过 Claude 进行自然语言领域查询

    • 自动域名建议工作流程

    • 根据可用性进行智能推荐

演示

00:00 -检查 google.com 的可用性
测试知名的高级域名以演示域名检查功能和替代 TLD 建议。

00:20 -测试 myawesomesite.com
验证自定义域名的可用性并探索替代扩展选项。

00:40 -验证 techstartup2026.io
探索科技初创域名选项并检查多个 TLD 扩展的可用性。

01:00 -分析 aitools 域名
检查竞争激烈的人工智能行业领域并分析初创企业命名的市场可用性。

要求

  • Python 3.10 或更高版本

  • 克劳德桌面

  • uv包管理器

依赖项安装

使用以下方法之一安装 uv 包管理器：

官方安装程序（推荐）：

curl -LsSf https://astral.sh/uv/install.sh | sh

Homebrew（macOS / Linux）：

brew install uv

安装 Homebrew（如果需要）：

  • 请访问https://brew.sh获取所有操作系统的安装说明

  • 或者运行： /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

MCP 服务器通过 uvx 自动管理 Python 依赖项。

安装

零克隆安装（推荐）

MCP 域可用性检查器支持直接安装而无需克隆存储库，使用 uvx 进行包管理。

配置

Claude Desktop 配置文件位于：

  • macOS ： ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows ： %APPDATA%\Claude\claude_desktop_config.json

  • Linux ： ~/.config/Claude/claude_desktop_config.json

编辑此文件以添加域可用性 MCP 配置：

{
  "mcpServers": {
    "mcp-domain-availability": {
      "command": "uvx",
      "args": [
        "--python=3.10",
        "--from",
        "git+https://github.com/imprvhub/mcp-domain-availability",
        "mcp-domain-availability"
      ]
    }
  }
}

如果您已经配置了其他 MCP，只需在“mcpServers”对象中添加“mcp-domain-availability”部分：

{
  "mcpServers": {
    "otherMcp": {
      "command": "...",
      "args": ["..."]
    },
    "mcp-domain-availability": {
      "command": "uvx",
      "args": [
        "--python=3.10",
        "--from",
        "git+https://github.com/imprvhub/mcp-domain-availability",
        "mcp-domain-availability"
      ]
    }
  }
}

通过 Smithery 安装

要通过Smithery自动为 Claude Desktop 安装 mcp-domain-availability：

npx -y @smithery/cli install @imprvhub/mcp-domain-availability --client claude

手动安装

对于开发或本地测试：

  1. 克隆存储库：

git clone https://github.com/imprvhub/mcp-domain-availability
cd mcp-domain-availability

  1. 安装依赖项：

uv sync

  1. 本地运行：

uv run src/mcp_domain_availability/main.py

工作原理

MCP 域名可用性检查器使用多种验证方法来确定域名可用性：

  1. DNS 解析：检查域名是否解析为 IP 地址

  2. WHOIS 查询：查询 WHOIS 数据库以获取注册信息

  3. 套接字连接：当其他方法不可用时，回退到基于套接字的检查

该工具结合这些方法的结果来提供准确的可用性状态，并通过并行处理同时检查多个域。

可用工具

域名检查

工具名称

描述

用法

check_domain

使用 --domain 标志检查域可用性

mysite.com --domain或mysite --domain

支持的 TLD 类别

热门顶级域名 (12)

com、net、org、io、ai、app、dev、co、xyz、me、info、biz

国家顶级域名 (35)

us、uk、ca、au、de、fr、it、es、nl、jp、kr、cn、in、br、mx、ar、cl、co、pe、ru、pl、cz、ch、at、se、no、dk、fi、be、pt、gr、tr、za、eg、ma、ng、ke

新顶级域名

技术、在线、站点、网站、商店、店铺、云、数字、博客、新闻等。

示例用法

以下是如何使用 Claude 进行 MCP 域可用性检查的示例：

单域检查

Check if mysite.com is available using --domain

域名研究

Check availability for "startup" across all TLDs using --domain

特定域验证

Is awesome.io available? Use --domain to check

输出格式

该工具提供全面的结果，包括：

  • 请求的域名：查询的确切域名的状态（如果提供了特定的 TLD）

  • 可用域名：按字母顺序排列的可用域名列表

  • 不可用域名：已注册域名列表

  • 摘要统计：按 TLD 类别细分（热门、国家、新 TLD）

  • 性能指标：检查每个域的持续时间

故障排除

“服务器断开连接”错误

如果您在 Claude Desktop 中看到连接错误：

  1. 验证 uvx 安装：

    • 运行uvx --version以确保 uvx 已正确安装

    • 如有必要，重新安装 uv： curl -LsSf https://astral.sh/uv/install.sh | sh

  2. 检查 Python 版本：

    • 确保 Python 3.10+ 可用： python3 --version

DNS解析问题

如果域检查失败：

  1. 网络连接：

    • 验证互联网连接是否稳定

    • 检查 DNS 服务器是否可访问

  2. 速率限制：

    • 大量批量检查可能会达到 DNS/WHOIS 服务的速率限制

    • 该工具使用信号量将并发请求限制为 20

配置问题

如果 MCP 服务器未启动：

  1. 验证配置语法：

    • 确保claude_desktop_config.json中的 JSON 语法有效

    • 检查所有括号和引号是否正确匹配

  2. 重启 Claude 桌面：

    • 配置更改后关闭并重新启动 Claude Desktop

Related MCP server: Domain Finder MCP Server

发展

项目结构

  • main.py ：包含 MCP 服务器和域检查逻辑的主入口点

  • 使用 DNS、WHOIS 和套接字回退方法的域名检查功能

  • 使用分类列表进行 TLD 管理

  • 并行域检查的异步处理

建筑

uv build

测试

uv run pytest

本地开发

uv run main.py

安全注意事项

MCP 域名可用性检查器会向 DNS 服务器和 WHOIS 服务发出外部网络请求。用户应注意：

  • DNS 提供商可能会记录域名查询

  • WHOIS 查询通常会被记录，并且可能会受到频率限制

  • 除了被检查的域名之外，不会传输任何个人信息

  • 所有查询都是只读的，不会修改任何外部系统

贡献

欢迎贡献！需要改进的地方包括：

  • 添加对其他 TLD 类别的支持

  • 实现缓存机制以实现更快的重复查询

  • 增强 WHOIS 解析以获取更详细的域名信息

  • 改进错误处理和重试机制

执照

该项目根据 Mozilla 公共许可证 2.0 获得许可 - 有关详细信息，请参阅LICENSE文件。

相关链接

Available Tools

1 tool
check_domainA
Check domain availability. 

Usage examples:
- "mysite.com --domain" - checks exact domain
- "mysite --domain" - checks mysite across all popular TLDs
- "test.io --domain" - checks test.io exactly, plus test across all TLDs

Args:
    domain_query (str): Domain to check with --domain flag
    
Returns:
    Dict containing availability results for the domain and suggested alternatives
ParametersJSON Schema
NameRequiredDescriptionDefault
domain_queryYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes what the tool does (checks availability, returns results and alternatives) and provides usage examples that clarify behavior with different input formats. However, it doesn't mention rate limits, authentication needs, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (purpose statement, usage examples, args, returns) and every sentence adds value. It's appropriately sized for a single-parameter tool with complex behavior, avoiding unnecessary verbosity while being comprehensive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (domain checking with TLD variations), no annotations, and an output schema present, the description provides excellent context. It explains the tool's behavior, parameter usage, and return format, making it complete enough for effective use without needing to reference the output schema for basic understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, so the description must fully compensate. It successfully explains the single parameter's purpose ('Domain to check'), provides multiple usage examples showing how different inputs affect behavior, and clarifies the --domain flag context, adding significant value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Check') and resource ('domain availability'), making it immediately understandable. It distinguishes this as a domain checking tool, which is unambiguous even without sibling tools for comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides usage examples that imply when to use the tool (for domain availability checks), but it doesn't explicitly state when NOT to use it or mention alternatives. Without sibling tools, this is less critical, but the guidance remains implicit rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedcheck_domain
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'check_domain' has a clear, distinct purpose that cannot be mistaken for any other functionality.

Naming Consistency5/5

The naming is perfectly consistent as there is only one tool following a clear verb_noun pattern ('check_domain'). No mixed conventions or deviations exist to evaluate.

Tool Count2/5

A single tool is too few for a server that appears to handle domain availability checking, as this domain typically involves related operations like bulk checks, WHOIS lookups, or domain suggestion generation. The tool count feels thin and incomplete for the apparent scope.

Completeness2/5

The tool surface is severely incomplete for domain availability checking. While 'check_domain' covers basic availability queries, there are significant gaps such as no tools for WHOIS information, bulk domain checks, domain suggestion algorithms, or TLD-specific searches, which are common in this domain and will limit agent effectiveness.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

  • Whodis MCP Server

    vinsidious
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that enables AI assistants to check domain name availability using WHOIS lookups.
    4 npm
    4
    ISC

  • Domain Finder MCP Server

    halfaipg
    A
    license
    Not graded
    quality
    D
    maintenance
    Intelligent domain name suggestion service that checks real-time availability across multiple providers and works with MCP-compatible tools like Cursor and Claude Code.
    13
    Apache 2.0

  • Whoisfreaks

    WhoisFreaks
    F
    license
    Not graded
    quality
    A
    maintenance
    A Model Context Protocol (MCP) server that exposes the full WhoisFreaks API suite as AI-callable tools. Works with Claude Desktop, Cursor, Windsurf, VS Code, Continue, Zed, and any other MCP-compatible AI client.
    -

  • internet-bs-mcp

    WannaBeGeekster
    A
    license
    Not graded
    quality
    C
    maintenance
    A Model Context Protocol server for Internet.bs domain registrar API. Enables checking availability, registering, renewing, and managing domains and DNS from Claude or any MCP client.
    MIT

Appeared in Searches