WHOIS Domain Lookup MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token, obtained from console.apify.com/account/integrations. The server lists its tool without a token, but a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_domain_whoisA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.