Skip to main content
Glama
Sign In
mambalabsdev

WHOIS Domain Lookup MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

WHOIS Domain Lookup MCP Server

npm version license

An MCP server for the Mamba Labs WHOIS Domain Lookup actor on Apify. Give it domains, website URLs, or email addresses. For each domain it returns one row: whether it is registered, the registrar, the creation, update, and expiry dates, the domain age and days until expiry, the status codes, the nameservers, DNSSEC, and the registrant organization and country where the registry publishes them.

What's Inside

Related MCP server: DomainDetails MCP Server

What it does

The actor asks each registry directly: its RDAP server from the official IANA list, a registry RDAP server the list does not carry yet for .io, .ac, .co, .us, .ch, and .li, and the registry's port 43 WHOIS server for the rest. No key and no third party lookup service. A domain the registry does not hold returns registered false. All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-whois-domain-lookup": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-whois-domain-lookup"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The lookup_domain_whois tool appears.

Prerequisites

Example prompts

  • "How old are these 200 prospect domains, and which ones expire in the next 90 days?"

  • "Who is the registrar for acme.io, and when was it registered?"

  • "Which of these domains are not registered?"

Tool

lookup_domain_whois. One tool. Example arguments:

{
  "domains": ["stripe.com", "notion.io", "lemonde.fr"]
}

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults. Numbers and yes or no options are sent as strings.

Input

Type

Description

domains

array

Domains, URLs, or email addresses, up to 5,000

domain

string

One domain

follow_registrar_rdap

string

true (default) or false

include_raw

string

true or false (default)

max_charge_usd

string

Optional cost cap for the run

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

Event

Free plan

Bronze

Silver

Gold

domain-lookup, per domain the registry answered for

$0.0025

$0.002375

$0.00225

$0.002125

apify-actor-start, per run start

$0.0006

$0.0006

$0.0006

$0.0006

Rows with no dates published, error rows, input that is not a domain, and repeats of a domain in the same run are free.

Your keys

The actor needs no key and holds none. It reads the registries' public RDAP and WHOIS services. Mamba Labs pays the platform costs of the run.

Full actor documentation

apify.com/mambalabs/whois-domain-lookup

License

MIT. See LICENSE.

Available Tools

1 tool
lookup_domain_whoisLook up domain WHOIS and RDAP recordsA
Read-onlyIdempotent

Look up who registered a domain, when, and when it expires. Give domains, website URLs, or email addresses (up to 5,000). For each registrable domain the actor asks the registry's own RDAP server (from the IANA list), or its port 43 WHOIS server where there is no RDAP, and returns one row: registered true or false, registrar, created_at, updated_at, expires_at, domain_age_days, days_until_expiry, status codes, nameservers, dnssec, and the registrant organization and country where the registry publishes them. Rows with no dates published, error rows, and input that is not a domain come back free with a row_status saying so. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per domain lookup.

NameRequiredDescriptionDefault
domainNoOne domain, URL, or email address, for example stripe.com.
domainsNoDomains, website URLs, or email addresses, up to 5,000. Subdomains are looked up as their registrable domain.
include_rawNotrue puts the registry's raw RDAP JSON or WHOIS text in raw_response. Default false.
max_charge_usdNoOptional. The run stops before a charge would pass this amount.
follow_registrar_rdapNotrue (default) also reads the registrar's RDAP record for the abuse email and any registrant details it publishes.

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/open-world, and the description adds substantial context beyond them: it requires an APIFY_TOKEN, Apify charges per domain lookup, max_charge_usd caps spend, non-success runs return an error with a run ID, and unpriced/failed/invalid rows come back free with a row_status. This is exactly the sort of cost and failure-mode disclosure an agent needs before calling.

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

Conciseness4/5

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

Front-loaded with purpose, then progressively deepens into sources, return fields, and cost behavior — good information ordering. It is dense with long clauses (the return-field list is a long run-on), but nearly every sentence earns its place.

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?

With no output schema, the description carries the full burden of explaining returns and does so thoroughly: it enumerates the row fields (registered flag, registrar, timestamps, age, expiry, status codes, nameservers, dnssec, registrant org/country) and describes row_status for degenerate rows. Nothing material is missing for correct invocation.

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?

Schema description coverage is 100%, so every parameter (domain, domains, include_raw, max_charge_usd, follow_registrar_rdap) is already documented. The description reinforces the 5,000 cap and the RDAP/WHOIS source selection but adds no syntax or format detail the schema lacks; baseline 3 applies.

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?

Opens with a specific verb and resource ('Look up who registered a domain, when, and when it expires') and then names the underlying data sources (registry RDAP from the IANA list, port 43 WHOIS fallback). An agent knows exactly what this tool produces without opening the schema.

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?

Conveys clear usage context: accepts domains, website URLs, or email addresses, up to 5,000 at a time, and subdomains are normalized to their registrable domain. There are no sibling tools to differentiate against, but it doesn't state when *not* to use it (e.g., bulk-vs-single tradeoffs, or when a cheaper alternative exists).

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 observedlookup_domain_whois
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.4/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is nothing to confuse it with. Its name and description make the single capability (registrant/expiry lookup for domains) unmistakable.

Naming Consistency5/5

The lone tool follows a clear verb_noun snake_case convention (lookup_domain_whois). There is no mixed convention to evaluate against, and the name is self-describing.

Tool Count3/5

The server's scope is narrow (read-only WHOIS/RDAP lookup), so a single tool is defensible, but it is thin: batch submission and result retrieval are fused into one call, and there is no companion tool for polling or re-fetching a run.

Completeness4/5

The lookup itself is thorough, returning registrar, dates, status, nameservers, DNSSEC, and partial registrant data with per-row status for failures. The gap is lifecycle: a failed run returns a run ID but there is no tool to check that run's status or retrieve its output.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Whois MCP

    modelcontextprotocol-servers
    A
    license
    B
    quality
    D
    maintenance
    Enables AI agents to perform WHOIS lookups to retrieve domain registration details, including ownership, registration dates, and availability status without requiring browser searches.
    4
    30 npm
    21
    MIT

  • domain-rdap-mcp

    Lulu-The-Narwhal
    A
    license
    A
    quality
    D
    maintenance
    Enables real-time domain registration lookups via RDAP, including availability, expiration, and registrar details, with no API key required. Supports natural language queries like 'is example.com available?' or 'when does example.com expire?'.
    1
    MIT