Skip to main content
Glama
badchars

osint-mcp-server

by badchars

whois_domain

Perform WHOIS/RDAP lookups to retrieve domain registration details including registrar, dates, nameservers, and contact information for OSINT investigations.

Instructions

RDAP/WHOIS lookup for a domain. Returns registrar, registration/expiration dates, nameservers, and contact entities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name to look up

Implementation Reference

  • The handler function whoisDomain performs the RDAP lookup for a given domain and processes the results.
    export async function whoisDomain(domain: string): Promise<RdapDomainResult> {
      await limiter.acquire();
      const res = await fetch(`https://rdap.org/domain/${domain}`);
      if (!res.ok) throw new Error(`RDAP domain lookup failed: ${res.status} ${res.statusText}`);
      const data = await res.json();
    
      const nameservers: string[] = [];
      if (data.nameservers) {
        for (const ns of data.nameservers) {
          if (ns.ldhName) nameservers.push(ns.ldhName);
        }
      }
    
      const entities: RdapDomainResult["entities"] = [];
      if (data.entities) {
        for (const ent of data.entities) {
          const roles = ent.roles ?? [];
          const vcard = ent.vcardArray?.[1];
          let name: string | undefined;
          let email: string | undefined;
          let phone: string | undefined;
    
          if (vcard) {
            for (const field of vcard) {
              if (field[0] === "fn") name = field[3];
              if (field[0] === "email") email = field[3];
              if (field[0] === "tel") phone = field[3];
            }
          }
    
          for (const role of roles) {
            entities.push({ role, name, email, phone });
          }
        }
      }
    
      // Extract dates from events
      let registrationDate: string | undefined;
      let expirationDate: string | undefined;
      let lastUpdated: string | undefined;
    
      if (data.events) {
        for (const evt of data.events) {
          if (evt.eventAction === "registration") registrationDate = evt.eventDate;
          if (evt.eventAction === "expiration") expirationDate = evt.eventDate;
          if (evt.eventAction === "last changed") lastUpdated = evt.eventDate;
        }
      }
    
      // Extract registrar from entities
      let registrar: string | undefined;
      const registrarEntity = data.entities?.find((e: any) => e.roles?.includes("registrar"));
      if (registrarEntity?.vcardArray?.[1]) {
        const fn = registrarEntity.vcardArray[1].find((f: any) => f[0] === "fn");
        if (fn) registrar = fn[3];
      }
    
      return {
        domain: data.ldhName ?? domain,
        status: data.status ?? [],
        registrar,
        registrationDate,
        expirationDate,
        lastUpdated,
        nameservers,
        entities,
        port43: data.port43,
      };
    }
  • Interface defining the shape of the whoisDomain output.
    interface RdapDomainResult {
      domain: string;
      status: string[];
      registrar?: string;
      registrationDate?: string;
      expirationDate?: string;
      lastUpdated?: string;
      nameservers: string[];
      entities: { role: string; name?: string; email?: string; phone?: string }[];
      port43?: string;
    }
  • Registration of the whois_domain MCP tool in the protocols definition file.
    const whoisDomainTool: ToolDef = {
      name: "whois_domain",
      description: "RDAP/WHOIS lookup for a domain. Returns registrar, registration/expiration dates, nameservers, and contact entities.",
      schema: {
        domain: z.string().describe("Domain name to look up"),
      },
      execute: async (args) => json(await whoisDomain(args.domain as string)),
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the type of lookup (RDAP/WHOIS) and what data is returned, but doesn't cover important aspects like rate limits, authentication requirements, error conditions, or whether it's a read-only operation (though implied by 'lookup').

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 perfectly concise - one sentence that efficiently communicates the action, target, and return data. Every word earns its place with zero waste or redundancy.

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

Completeness3/5

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

For a single-parameter lookup tool with no annotations and no output schema, the description covers the basic purpose and return data structure adequately. However, it lacks guidance on usage context and behavioral details that would be helpful for an agent.

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?

The schema has 100% description coverage, so the baseline is 3. The description adds value by specifying this is for domain lookups (not IPs), which helps clarify the 'domain' parameter's purpose beyond what the schema provides. However, it doesn't add format details or constraints.

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 specific action ('RDAP/WHOIS lookup') and resource ('for a domain'), and distinguishes it from sibling tools like 'whois_ip' by specifying domain lookup rather than IP lookup. It provides a complete picture of what the tool does.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'st_whois' or 'vt_domain' from the sibling list. It states what it does but offers no context about when it's the appropriate choice among similar tools.

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/badchars/osint-mcp-server'

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