Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

network_whois

Query authoritative WHOIS servers for domain or IP registration records. Retrieve registrar, creation/expiry dates, name servers, and ownership details.

Instructions

Whois Lookup. Outbound WHOIS lookup: queries an authoritative WHOIS server (TCP port 43, or a registered remote worker when one is healthy) for the registration or allocation record of a domain name or public IP address. Returns registrar, creation/expiry dates, name servers, domain status, the full raw WHOIS text, and a parsed key/value map. Use this for ownership, registrar, and registration-record data. Prefer osint_domain_age when you only need the registration/expiry dates and computed age; prefer network_dns for live A/MX/NS/TXT records; prefer network_reverse_dns for IP-to-hostname (PTR); prefer network_asn_lookup for autonomous-system / network-owner data. Makes a live external network call and depends on third-party WHOIS servers, so results are not cached and not idempotent; it is non-destructive and read-only with respect to this service. Rate limited (anonymous 2/min, 10/hour, 30/day; authenticated 5/50/200) with a CAPTCHA challenge after 5 requests/hour.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesDomain name or public IP address to look up, for example youtube.com or 8.8.8.8. Private, reserved, and loopback hosts are rejected; the value is validated and capped at 255 bytes.
worker_idNoOptional registered healthy worker peer ID. Omit to use the default master-server behavior.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoThe domain name or IP address that was queried.
serverNoWHOIS server that answered the query, for example whois.verisign-grs.com or whois.arin.net.
raw_outputNoFull unparsed WHOIS response text exactly as returned by the upstream server.
parsedNoLowercased key/value map of every parsed WHOIS field, plus a common_fields sub-object normalizing domain_name, registrar, creation_date, expiration_date, name_servers, and status.
timestampNoISO 8601 timestamp of when the lookup completed.
Behavior1/5

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

Contradiction with annotations: description claims 'non-destructive and read-only with respect to this service', but annotations set readOnlyHint=false. This inconsistency undermines transparency.

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?

Front-loaded with purpose, then clear usage guidance, then behavioral details, all in a compact paragraph. Every sentence adds value.

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 the complexity (live network call, rate limits, third-party dependency), the description covers purpose, usage, behavior, parameters, limitations, and return value. Output schema exists but description already mentions returns.

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 is 100%, and the description adds validation details (rejected private/reserved/loopback hosts, 255-byte cap) beyond the schema descriptions.

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?

Specific verb 'Whois Lookup' and resource 'domain name or public IP address' clearly state what the tool does. Distinguishes from siblings like osint_domain_age, network_dns, etc.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool (ownership, registrar, registration-record data) and provides alternatives (osint_domain_age, network_dns, network_reverse_dns, network_asn_lookup) with clear reasons.

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/Jambozx/onlinecybertools-mcp-server'

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