Skip to main content
Glama
bingal

FastDomainCheck MCP Server

by bingal
OverviewSchemaRelated ServersScoreDiscussions
Python

FastDomainCheck MCP Server (Python)

This is a domain availability check server implemented using Python and the Model Context Protocol (MCP). It provides MCP Tools to check if single or multiple domain names are already registered.

Features

  • Bulk domain registration status checking

  • Dual verification using WHOIS and DNS

  • Support for IDN (Internationalized Domain Names)

  • Concise output format

  • Built-in input validation and error handling

Related MCP server: Domain Checker MCP Server

Tool Documentation

check_domains

Check registration status for multiple domain names.

Input Format

{
  "domains": ["example.com", "test.com"]
}

Parameters:

  • domains: Array of strings containing domain names to check

    • Maximum length of 255 characters per domain

    • Maximum 50 domains per request

    • No empty domain names allowed

Output Format

{
  "results": {
    "example.com": {
      "registered": true
    },
    "test.com": {
      "registered": false
    }
  }
}

Response Fields:

  • results: Object with domain names as keys and check results as values

    • registered: Boolean

      • true: Domain is registered

      • false: Domain is available

Error Handling

The tool will return an error in the following cases:

  1. Empty domains list

  2. More than 50 domains in request

  3. Empty domain name

  4. Domain name exceeding 255 characters

  5. Result serialization failure

Error Response Format:

{
  "error": "Error: domains list cannot be empty"
}

Usage Examples

Check multiple domains:

Request

{
  "domains": ["example.com", "test123456.com"]
}

Response

{
  "results": {
    "example.com": {
      "registered": true
    },
    "test123456.com": {
      "registered": false
    }
  }
}

MCP Server Settings

Configuring FastDomainCheck MCP in Claude Deskto

Modify your claude-desktop-config.json file as shown below

{
  "mcpServers": {
    "fastdomaincheck": {
      "command": "uvx",
      "args": [
        "fastdomaincheck-mcp-server"
      ]
    }
  }
}

Go Version Reference

go version

Contributing

Feel free to open issues or submit pull requests.

License

MIT License (You should add a LICENSE file, typically containing the MIT license text)

Available Tools

1 tool
check_domainsA
Check if multiple domain names are registered.

Usage:
    Input: A list of domain names to check (e.g. ["example.com", "test.com"])
    Output: JSON object containing registration status of each domain:
    {
      "results": {
        "example.com": {
          "registered": true
        },
        "test.com": {
          "registered": false
        }
      }
    }
ParametersJSON Schema
NameRequiredDescriptionDefault
domainsYes

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided, so description must cover behavior. It discloses input/output format but doesn't mention authentication, rate limits, or side effects. The tool is read-only, but that's not explicitly claimed.

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 concise with clear sections for usage, input, and output. Every sentence adds value without any fluff.

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 simple single-param tool with no output schema, the description fully explains input format, output structure, and purpose. No gaps remain.

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

Parameters4/5

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

Schema has 1 param 'domains' with no description. The description adds meaning with an example and explicitly states it should be a list of domain names, compensating for 0% schema coverage.

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 checks if multiple domain names are registered, with a specific verb and resource, and distinguishes it from any potential siblings by being explicit about the action.

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

Usage Guidelines4/5

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

The description provides explicit usage context: input list of domains, output registration status. No siblings exist, so no exclusions needed, but it could mention when _not_ to use (e.g., single domain). Still clear.

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. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.12
    • First observedcheck_domains
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.5/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The purpose is singular and clear.

Naming Consistency5/5

The single tool name 'check_domains' follows a verb_noun pattern, which is consistent with itself. No other tools to create inconsistency.

Tool Count5/5

The server is dedicated exclusively to checking domain registration status. One tool is perfectly sufficient and well-scoped for this narrow purpose.

Completeness5/5

The tool fully covers the server's stated function of checking domain registration. There are no missing operations because the task is atomic and does not require CRUD or additional lifecycle actions.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Domain Checker

    ahramadan44
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables checking domain name availability using WHOIS lookups and DNS resolution. Supports both single and batch domain checking with detailed availability analysis.
    -

  • Domain Checker MCP Server

    ajot
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables domain availability checking through dual verification using WHOIS lookups and DNS resolution. Supports both single and batch processing to provide detailed analysis on whether domains are likely available or already registered.
    4
    -

  • domain-mcp

    cfenzo
    F
    license
    A
    quality
    D
    maintenance
    Enables domain name availability checking through DNS and WHOIS lookups with confidence scoring. It supports searching across alternative TLDs and generating domain name variations for branding purposes.
    4
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bingal/fastdomaincheck-mcp-server-python'

If you have feedback or need assistance with the MCP directory API, please join our Discord server