Skip to main content
Glama
OrtaMarco

domain-security-mcp-server

by OrtaMarco

WHOIS Lookup

whois_lookup
Read-onlyIdempotent

Retrieve domain registration details including registrar, creation/expiry dates, name servers, and status via raw WHOIS protocol. No API key required.

Instructions

Look up domain registration data over the raw WHOIS protocol (port 43): registrar, creation/update/expiry dates, name servers and domain status. Resolves the correct WHOIS server via IANA and follows registrar referrals. No API key.

Args:

  • domain (string): the domain to look up.

  • response_format ('markdown' | 'json'): output format (default 'markdown'). JSON includes the raw WHOIS text.

Returns: { domain, registrar, created, updated, expires, name_servers[], status[], whois_server }.

Example: "Who is the registrar for openai.com and when does it expire?" -> whois_lookup(domain="openai.com"). Errors: returns an error if no WHOIS server answers (some ccTLDs restrict or rate-limit WHOIS).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to look up, e.g. 'example.com'.
response_formatNoOutput format: 'markdown' for a human-readable summary (default) or 'json' for the full structured payload.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
whois_serverNo
registrarNo
createdNo
updatedNo
expiresNo
name_serversYes
statusYes
registrant_orgNo
rawYes
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds valuable details: no API key, IANA referral resolution, return structure, error conditions. Adds context beyond annotations.

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?

Compact 7 sentences with clear sections: overview, args, returns, example, errors. No fluff, front-loaded with key action.

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 output schema, annotations, and parameter schema coverage, description is complete: covers function, parameters, return, errors, and limitations. No gaps.

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 coverage 100% so baseline 3. Description adds default for response_format, clarifies JSON includes raw WHOIS text, and explains domain parameter. Adds meaning beyond 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?

Description clearly states it looks up domain registration data via raw WHOIS protocol (port 43) and lists returned fields. Distinguishes from siblings like DNS lookups or email checks by specifying raw WHOIS protocol.

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?

Description implies usage for domain registration queries with an example, but does not explicitly differentiate when to use this vs. sibling tools like dns_lookup or mx_lookup. No direct comparison or excluded scenarios.

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

Install Server

Other Tools

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/OrtaMarco/domain-security-mcp-server'

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