Skip to main content
Glama
simplebytes-com

DomainDetails MCP Server

by simplebytes-com
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

DomainDetails MCP Server

A Model Context Protocol (MCP) server that provides comprehensive domain research tools including RDAP, WHOIS, and DNS lookup capabilities.

Features

  • RDAP First: Uses modern RDAP protocol for structured domain data

  • WHOIS Fallback: Automatically falls back to WHOIS when RDAP fails

  • Registry Detection: Automatically detects the correct RDAP/WHOIS server for any TLD

  • Comprehensive Coverage: Supports 50+ TLDs including gTLDs and ccTLDs

  • Easy Integration: Works with any MCP-compatible client (Claude Desktop, IDEs, etc.)

Related MCP server: rdap-mcp

Installation

npm install domaindetails-mcp

Or use directly with npx:

npx domaindetails-mcp

Usage

Claude Desktop

Add to your Claude Desktop configuration file:

MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "domaindetails": {
      "command": "npx",
      "args": ["-y", "domaindetails-mcp"]
    }
  }
}

Claude Code

Add to your Claude Code MCP settings:

claude mcp add domaindetails -- npx -y domaindetails-mcp

Or manually add to ~/.claude/claude_desktop_config.json:

{
  "mcpServers": {
    "domaindetails": {
      "command": "npx",
      "args": ["-y", "domaindetails-mcp"]
    }
  }
}

Cursor

Add to your Cursor MCP configuration at ~/.cursor/mcp.json:

{
  "mcpServers": {
    "domaindetails": {
      "command": "npx",
      "args": ["-y", "domaindetails-mcp"]
    }
  }
}

Windsurf

Add to your Windsurf MCP configuration at ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "domaindetails": {
      "command": "npx",
      "args": ["-y", "domaindetails-mcp"]
    }
  }
}

Other MCP Clients

For any MCP-compatible client, use:

  • Command: npx

  • Args: ["-y", "domaindetails-mcp"]

Or if installed globally:

  • Command: domaindetails-mcp

Available Tools

domain_lookup

Look up comprehensive domain information using RDAP protocol with WHOIS fallback.

Parameters:

  • domain (string, required): The domain name to look up (e.g., example.com)

  • prefer_whois (boolean, optional): If true, use WHOIS instead of RDAP as primary method

  • include_raw (boolean, optional): If true, include raw protocol response data

Example Response:

{
  "domain": "example.com",
  "found": true,
  "method": "rdap",
  "timestamp": "2025-01-21T10:30:00Z",
  "status": ["client transfer prohibited"],
  "nameservers": ["ns1.example.com", "ns2.example.com"],
  "rdap": {
    "registration_date": "1995-08-14T04:00:00Z",
    "expiration_date": "2025-08-13T04:00:00Z",
    "contacts": [...],
    "dnssec": {...}
  }
}

Supported TLDs

The server includes built-in registry detection for 50+ TLDs:

Generic TLDs: com, net, org, info, biz, name, pro, xyz, top, site, online, tech, store, app, dev, io, ai, co, me, tv, cc

Country Code TLDs: uk, ca, au, de, fr, nl, be, ch, at, it, es, se, no, dk, fi, ie, pl, cz, sk, hu, ro, bg, hr, si, lv, lt, ee

For unsupported TLDs, the server will attempt to fetch registry information from IANA's bootstrap service.

Related Packages

  • domaindetails - CLI tool and library for domain lookups (includes this MCP server)

Development

# Clone repository
git clone https://github.com/simplebytes-com/domaindetails-mcp.git
cd domaindetails-mcp

# Install dependencies
npm install

# Build
npm run build

# Test locally
node build/index.js

License

MIT

Support

For issues and questions:

Related Projects

Available Tools

1 tool
domain_lookupA

Look up domain information using RDAP protocol with WHOIS fallback. Provides comprehensive domain registration details, nameservers, contacts, and status information.

ParametersJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain name to look up (e.g., example.com)
include_rawNoIf true, include raw protocol response data in the result
prefer_whoisNoIf true, use WHOIS instead of RDAP as the primary lookup method

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the burden falls on the description. It discloses the use of RDAP and WHOIS and the type of information returned, which is useful. However, it doesn't describe error behavior (e.g., what happens if RDAP and WHOIS both fail), rate limits, or the raw response structure, leaving some behavioral uncertainty.

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 a compact two-sentence summary that front-loads the primary action and then lists key result categories. No redundant phrases or filler.

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

Completeness4/5

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

The description covers the tool's core purpose and the main data categories returned, which is sufficient for a three-parameter lookup tool. It falls short of explaining potential failure modes or the exact shape of the output, but given the absence of an output schema and the simplicity of the operation, this is a minor gap.

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

Parameters3/5

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

All three parameters are well-described in the schema (domain, include_raw, prefer_whois) with clear documentation. The description adds context by explaining the fallback mechanism, which indirectly clarifies the purpose of prefer_whois, but this is marginal beyond the schema. Since schema coverage is 100%, the baseline of 3 is appropriate.

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 function with the verb 'Look up' and specifies the resource as 'domain information.' It distinguishes the method by naming RDAP and WHOIS fallback, and lists the types of details returned (registration, nameservers, contacts, status). This is specific and aligns with the tool name.

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?

No explicit usage guidance is provided. There are no sibling tools to compare with, and the description doesn't state when to choose this tool over alternatives or when not to use it. The context implies it's for domain lookups, but the fallback behavior and parameter options (include_raw, prefer_whois) are not framed as decision points.

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 updatev1.2.0
    • First observeddomain_lookup
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion. The tool's purpose is clearly stated and unique.

Naming Consistency5/5

The tool name 'domain_lookup' follows a clear, readable pattern and is appropriate for its function. With a single tool, there is no inconsistency.

Tool Count4/5

The server is focused on domain details lookup, and a single tool adequately covers this narrow scope. While the typical range is 3-15, the simplicity of the purpose justifies the minimal count, making it slightly under but reasonable.

Completeness5/5

The tool provides comprehensive domain information via RDAP with WHOIS fallback, covering registration, nameservers, contacts, and status. There are no obvious missing operations for a lookup-only service.

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

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/simplebytes-com/domaindetails-mcp'

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