WhoisFreaks

● Active

io.github.WhoisFreaks/whoisfreaks-mcp-server

WHOIS, DNS, IP geolocation, SSL and domain intelligence from the WhoisFreaks API.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "whoisfreaks-mcp-server": {
      "url": "https://mcp.whoisfreaks.com/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http whoisfreaks-mcp-server https://mcp.whoisfreaks.com/mcp
VS Code
code --add-mcp '{"name":"whoisfreaks-mcp-server","type":"http","url":"https://mcp.whoisfreaks.com/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Search & Web
Version
2.1.0
Registry
active
Published
11/13/2026

Live check

checked Nov 19, 2026, 05:07 UTC
● Working500 msprotocol 2025-03-26v2.1.0tools

The endpoint answered the MCP handshake as "whoisfreaks-mcp-server" and listed 22 tools. Answering since Nov 18, 2026.

Context cost ≈ 11k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 22 tools.

Tools (22)

tool list changed Nov 19, 2026, 05:07 UTC
  • liveWhoisLookup2 params

    Get the current WHOIS registration record for a domain, queried live from WHOIS servers and RDAP. Use this to find who owns a domain now, its registrar, creation and expiry dates, name servers or status. For past owners and changes over time use whoisHistory. For many domains at once use bulkWhoisLookup. To find domains owned by a person, email or company use reverseWhoisLookup. To check whether an unregistered name can be bought use domainAvailability. Pass a bare domain (example.com), not a URL. Returns registrar and registry details, creation/update/expiry dates, registrant, admin and technical contacts (often privacy-redacted), name servers, domain status flags and the raw WHOIS text. When the registrar does not answer, the result is marked as a partial record (HTTP 206); when no live lookup works, as the latest stored record (HTTP 210). Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • domainNamestringrequiredDomain name to look up. Accepts: example.com | https://example.com | http://example.com
    • formatstringResponse format. Default: json
  • bulkWhoisLookup2 params

    Get the current WHOIS records of up to 100 domains in one request, queried live. Use this instead of calling liveWhoisLookup many times, for example to audit a domain portfolio or enrich a list of domains taken from logs. For one domain use liveWhoisLookup. Lists of more than 100 domains go in several calls; files of up to 3 million domains are handled by the Bulk Tool in the WhoisFreaks billing dashboard, not by this tool. Costs 1 credit per domain. A large batch can take a few minutes. Returns one WHOIS record per domain, with the same fields as liveWhoisLookup. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • domainNamesarrayrequiredDomain names to look up, at most 100. Example: ["whoisfreaks.com", "jfreaks.com"]
    • formatstringResponse format. Default: json
  • whoisHistory2 params

    Get the historical WHOIS records of a domain: deduplicated snapshots ordered from newest to oldest, going back as far as 1986. Use this to see previous owners, registrar transfers, past contacts, name server changes, or when a domain expired and was re-registered. For only the current record use liveWhoisLookup. For DNS changes over time use dnsHistory. Costs 2 credits. Every record comes back in one response; there are no pages. Returns a list of snapshots, each with the registrar, dates, contacts and name servers recorded at that time. A domain with no recorded history returns a "no data found" message. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • domainNamestringrequiredDomain name to look up history for. Examples: whoisfreaks.com | google.com
    • formatstringResponse format. Default: json
  • reverseWhoisLookup8 params

    Find domains whose WHOIS records contain a given email, registrant name or company, or whose name contains a keyword, across 4.6 billion WHOIS records. Use this to map everything a person or organisation has registered, for example when investigating a phishing actor or auditing a company's domain portfolio. Provide exactly one of email, owner, company or keyword. To look up the owner of one known domain use liveWhoisLookup. To find look-alike domains of a brand (typosquats) use domainDiscovery. mode=mini returns a short summary per domain and 100 domains per page, against 50 full records per page in the default mode. Costs 5 credits per page, so prefer mini when you only need the list of domains. Results are paginated: the response gives the total pages, and page selects the next one. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • emailstringSearch by registrant email address, exact or regex match. Example: admin@example.com
    • keywordstringSearch by text in the domain name. With exact=false (the default) it matches every domain whose name contains it. Example: google
    • ownerstringSearch by registrant/owner name, matched as a phrase unless exact=true. Example: John Doe
    • companystringSearch by company/organization name, matched as a phrase unless exact=true. Example: Alphabet Inc
    • modestring'default' (the default) returns the full WHOIS record of each domain, 50 per page. 'mini' returns only the domain name, creation/update/expiry dates and the reg
    • exactbooleanfalse (the default): keyword matches every domain that contains it, and owner and company match as a phrase. true: match the value exactly.
    • pageintegerPage number for paginated results. Default: 1
    • formatstringResponse format. Default: json
  • ipWhoisLookup2 params

    Get the registry WHOIS record for an IPv4 or IPv6 address: who the IP block is allocated to. Use this to find the owning organisation, CIDR range, AS number and abuse contact of an IP, for example to report abuse. For city, ISP and coordinates use ipGeolocation. For VPN, proxy, Tor and threat signals use ipSecurity. For details about the autonomous system itself use asnWhoisLookup. For domains hosted on the IP use reverseDnsLookup. Returns the network range (inetnum/inet6num) and CIDR, owning organisation and ASN, admin, technical and abuse contacts, route objects, and the raw WHOIS text. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • ipstringrequiredIPv4 or IPv6 address to look up. Examples: 8.8.8.8 | 2001:4860:4860::8888
    • formatstringResponse format. Default: json
  • asnWhoisLookup2 params

    Get the registry WHOIS record for an autonomous system (ASN): the network operator behind a set of IP routes. Use this when you have an AS number (for example from ipWhoisLookup or ipGeolocation output) and need the operator's name, country, contacts or the IP prefixes it announces. If you only have an IP address, call ipWhoisLookup first to get its ASN. Returns the organisation name and description, country of registration, announced IPv4 and IPv6 prefixes, peering information, admin and technical contacts, and AS sets and blocks. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • asnstringrequiredAutonomous System Number to look up. Accepts 'AS15169' or plain '15169'.
    • formatstringResponse format. Default: json
  • dnsLookup6 params

    Resolve a domain's current DNS records live: A, AAAA, MX, NS, CNAME, SOA, TXT and SPF. With ipAddress it also does a reverse (PTR) lookup of an IP address. Use this to see where a domain points now: its IP addresses, mail servers, name servers, or TXT records such as SPF, DKIM and DMARC. For how records changed over time use dnsHistory. To go the other way and find domains that use a given IP, mail server or name server use reverseDnsLookup. For many domains or IPs at once use bulkDnsLookup. type=all (the default) returns every record type in one call; pass one type or a short list such as mx,txt to keep the result small. cnameDepth follows CNAME chains, for example for www hosts behind a CDN. Returns the records grouped by type. Records reached through a CNAME carry the target's name: a DKIM key published through one, as Microsoft 365 does, comes back under the provider's host name. A domain's SPF policy (v=spf1) is listed as an SPF entry (type 99), apart from its other TXT records, even though domains publish it as an ordinary TXT record; the label isn't a sign of the obsolete SPF record type. A domain with no records of the requested type returns an empty list or a "no data found" message. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • domainNamestringDomain name to query DNS records for. Example: google.com. Optional when ipAddress is given.
    • ipAddressstringIP address for a reverse (PTR) lookup. Example: 8.8.8.8. Pass it instead of, or together with, domainName.
    • typestringRecord types to return: 'all' (the default), one type such as MX, or a comma-separated list such as a,mx,ns. Supported: A, AAAA, MX, NS, CNAME, SOA, TXT, SPF.
    • cnameDepthintegerHow many CNAME hops to follow before collecting records, 0 to 4. Default: 0
    • relativeRecordsbooleantrue (the default): include the records of CNAME targets. false: only the records on the queried name.
    • formatstringResponse format. Default: json
  • bulkDnsLookup5 params

    Resolve the current DNS records of up to 100 domains, and the PTR records of up to 100 IP addresses, in one request. Use this instead of calling dnsLookup many times, for example to check the mail servers of a list of domains or to name a list of IPs from logs. Provide domainNames, ipAddresses, or both. For one domain or IP use dnsLookup. Lists longer than 100 go in several calls; files of up to 3 million entries are handled by the Bulk Tool in the WhoisFreaks billing dashboard, not by this tool. Costs 1 credit per domain or IP. A large batch can take a few minutes. Returns one entry per domain or IP, with the same record fields as dnsLookup. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • domainNamesarrayDomain names to resolve, at most 100. Example: ["whoisfreaks.com", "jfreaks.com"]
    • ipAddressesarrayIP addresses for reverse (PTR) lookups, at most 100. Example: ["1.1.1.1", "8.8.8.8"]
    • typestringRecord types to return: 'all' (the default), one type such as MX, or a comma-separated list such as a,mx,ns. Supported: A, AAAA, TXT, NS, MX, SOA, SPF.
    • cnameDepthintegerHow many CNAME hops to follow before collecting records, 0 to 4. Default: 0
    • formatstringResponse format. Default: json
  • dnsHistory4 params

    Get the historical DNS records of a domain, showing how its A, MX, NS and other records changed over time. Use this for investigations and migrations: earlier hosting IPs (for example the origin IP behind a CDN), past mail servers, or name server changes. For the current records only use dnsLookup. For ownership changes use whoisHistory. Costs 2 credits per page. Returns past records with the dates they were observed. Results are paginated: raise page to get more, and filter by type to reduce output. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • domainNamestringrequiredDomain name to retrieve historical DNS records for. Example: whoisfreaks.com
    • typestringRecord types to return: 'all' (the default), one type such as A, or a comma-separated list such as a,mx,ns. Supported: A, AAAA, MX, NS, CNAME, SOA, TXT.
    • pageintegerPage number for paginated results. Default: 1
    • formatstringResponse format. Default: json
  • reverseDnsLookup7 params

    Find domains whose DNS records point to a given value: an IP address or range, mail server, name server or other record value. Use this to see which other sites share a hosting IP, which domains use a mail server or name server, or to map infrastructure during an investigation. Set type to match the value: a for an IPv4 address or range (default), aaaa for IPv6, mx for a mail server, ns for a name server. For a domain's own records use dnsLookup. For the registered owner of an IP block use ipWhoisLookup. exact=false (the default) enables '*' wildcard matching, for example *.cloudflare.com. sort=desc with sortBy=lastSeen puts the most recently seen domains first. Costs 5 credits per page of up to 100 domains. Popular IPs and name servers can match millions of domains, so use page and stop once you have enough. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • valuestringrequiredThe value to search for in DNS records: an IP address or CIDR range for A/AAAA (8.8.8.8 | 104.16.0.0/16), a host name for MX, NS or CNAME (mail.example.com), or
    • typestringOne DNS record type to search within. Default: a
    • exactbooleanfalse (the default): the value is matched as a pattern, where '*' matches any characters. true: exact match. Ignored for A and AAAA, which always match the IP o
    • pageintegerPage number for paginated results. Default: 1
    • sortstringSort the results by sortBy, ascending or descending. Omit for unsorted results.
    • sortBystringDate that sort orders by. Only used together with sort. Default: lastSeen
    • formatstringResponse format. Default: json
  • ipGeolocation1 param

    Look up where an IPv4 or IPv6 address is located and which network it belongs to. Use this for country, region, city, coordinates, ISP, ASN, connection type and local currency, for example to localise a visitor or see where a server is hosted. The location is an estimate and is most reliable at country level. For many IPs at once use bulkIpGeolocation. For VPN, proxy, Tor and threat signals use ipSecurity. For the registered owner of the IP block and its abuse contact use ipWhoisLookup. Private and reserved addresses (10.x, 192.168.x, 127.x and similar) cannot be geolocated and return a "non-routable IP" (HTTP 423) message. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • ipstringrequiredIPv4 or IPv6 address to geolocate. Examples: 8.8.8.8 | 2606:4700:4700::1111
  • bulkIpGeolocation1 param

    Look up the location and network of up to 100 IPv4 or IPv6 addresses in one request. Use this instead of calling ipGeolocation many times, for example to map the visitors or attackers in a log. For one IP use ipGeolocation. For threat signals on many IPs use bulkIpSecurity. Costs 1 credit per IP answered. Returns one entry per IP, with the same fields as ipGeolocation. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • ipsarrayrequiredIPv4 or IPv6 addresses to geolocate, at most 100. Example: ["1.1.1.1", "8.8.8.8"]
  • ipSecurity1 param

    Check the reputation of an IPv4 or IPv6 address: VPN, proxy (including residential), Tor exit node, privacy relay, spam and known-attacker activity, bots by type and operator, and whether it belongs to a cloud provider or a corporate secure web gateway. Use this for fraud checks, sign-up or login screening, or triaging a suspicious IP from logs. For many IPs at once use bulkIpSecurity. For location and ISP only use ipGeolocation. For the registered owner and abuse contact use ipWhoisLookup. Returns a threat score from 0 to 100, a flag and confidence score for each signal, provider names where known, and the IP's location, network (route, anycast, CDN) and ASN. A clean result means no signals were found, not that the IP is guaranteed safe. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • ipstringrequiredIPv4 or IPv6 address to run security analysis on. Examples: 1.1.1.1 | 185.220.101.0
  • bulkIpSecurity1 param

    Check the reputation of up to 100 IPv4 or IPv6 addresses in one request: VPN, proxy, Tor, relay, spam, known-attacker and bot signals for each. Use this instead of calling ipSecurity many times, for example to screen the IPs behind a wave of sign-ups or failed logins. For one IP use ipSecurity. For location only use bulkIpGeolocation. Costs 1 credit per IP answered. An invalid IP returns its own error entry while the other IPs still return results. Returns one entry per IP, with the same fields as ipSecurity. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • ipsarrayrequiredIPv4 or IPv6 addresses to check, at most 100. Example: ["1.1.1.1", "185.220.101.45"]
  • domainAvailability4 params

    Check whether a domain name is available to register, using both DNS and WHOIS data. Use this before suggesting or buying a domain name. Set suggestions=true to also get alternative names with other extensions, each marked available or not; count sets how many (5-100). To check a list of names, or one name across many extensions, use bulkDomainAvailability. For details about who owns a registered domain use liveWhoisLookup. Costs 1 credit, plus 1 credit per 5 suggestions. Returns the availability (AVAILABLE or UNAVAILABLE). With suggestions it returns a list of names instead, the domain asked about among them, each AVAILABLE or UNAVAILABLE. Availability can change at any moment, and this check does not reserve the domain. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • domainstringrequiredDomain name to check availability for. Example: whoisfreaks.com
    • suggestionsbooleanIf true, also return alternative domain names with other extensions and whether each is available. Default: false
    • countintegerNumber of suggestions to return when suggestions=true, 5 to 100. Default: 5
    • formatstringResponse format. Default: json
  • bulkDomainAvailability4 params

    Check whether many domain names can be registered, in one request: either up to 100 full domain names, or one name across up to 100 extensions (TLDs). Use this to pick an available name across extensions such as .com, .io and .ai (pass domain and tlds), or to check a list of candidate names (pass domainNames). For one name, or for name ideas, use domainAvailability with suggestions=true. Uses API credits for each domain checked. An invalid name returns its own error entry while the other names still return results. Returns each domain with its availability: AVAILABLE, UNAVAILABLE or UNKNOWN. Availability can change at any moment, and this check does not reserve anything. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • domainNamesarrayFull domain names to check, at most 100. Example: ["whoisfreaks.io", "jfreaks.pk"]. Leave out when you pass domain and tlds.
    • domainstringThe name to check across the extensions in tlds. Example: whoisfreaks.com. Use together with tlds.
    • tldsarrayExtensions (TLDs) to check the domain against, without the leading dot, at most 100. Example: ["io", "dev", "ai"]
    • formatstringResponse format. Default: json
  • subdomainLookup6 params

    List the known subdomains of a domain (for example api.example.com or mail.example.com) from the WhoisFreaks subdomain database. Use this for attack-surface mapping, finding exposed services, or auditing a company's hosts. It looks up subdomains already discovered by WhoisFreaks rather than scanning the target, so it only knows subdomains that have been observed. To get a subdomain's DNS records use dnsLookup. To find look-alike domains of a brand use domainDiscovery, and look-alike subdomains on other domains use subdomainTyposquatting. status=active keeps only subdomains that currently resolve; after and before (YYYY-MM-DD) filter by when a subdomain was discovered. Costs 2 credits per page. Results are paginated, so large domains may need several pages. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • domainstringrequiredDomain to find subdomains for. Example: whoisfreaks.com. A subdomain such as api.whoisfreaks.com returns the hosts beneath it.
    • statusstringFilter by subdomain status. Omit to return both active and inactive.
    • afterstringReturn subdomains first seen after this date (ISO format: YYYY-MM-DD). Must not be in the future or later than before. Example: 2023-01-01
    • beforestringReturn subdomains first seen before this date (ISO format: YYYY-MM-DD). Must not be in the future. Example: 2024-01-01
    • pageintegerPage number for paginated results. Default: 1
    • formatstringResponse format. Default: json
  • domainDiscovery4 params

    Find registered domains that look like typo variants of a brand name (typosquats such as paypa1.com or paypal-secure.net), or that match a wildcard pattern, across more than 1,500 TLDs. Use this for brand protection, phishing detection, or tracking look-alike registrations. Provide exactly one of keyword or pattern. For subdomains that imitate a brand on unrelated domains, such as login.paypa1.example.com, use subdomainTyposquatting. To find domains whose name simply contains a word use reverseWhoisLookup with keyword. To judge how risky a result is use domainReputation; for its owner use liveWhoisLookup. Costs 5 credits per page (100 domains by default). A search can take up to two minutes. Returns each domain with its creation, expiry and last-seen dates and whether it has been dropped, plus the total count. When there are more, the result has a nextPageToken: pass it as pageToken, with the same keyword or pattern, to get the next page. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • keywordstringBrand or name to find typo variants of: 3 to 63 letters, digits or hyphens, one label without a dot. Example: paypal (not paypal.com)
    • patternstringWildcard search instead of keyword: '*' matches any characters, at most 3 asterisks, at least 5 other characters and 63 in total. Example: *paypa*
    • pageTokenstringnextPageToken from the previous result, to get the next page. Pass the same keyword or pattern with it.
    • fetchSizeintegerDomains per page, 1 to 10000. Default: 100
  • subdomainTyposquatting4 params

    Find subdomains, on any domain, that contain a typo variant of a brand name or match a wildcard pattern as one of their labels, for example login.paypa1.example.com. Phishing pages often hide a brand inside a subdomain of an unrelated domain, so these hosts never show up in domainDiscovery. Use this for brand protection and phishing hunting. Provide exactly one of keyword or pattern. For the subdomains of one domain use subdomainLookup. To judge how risky a result's domain is use domainReputation. Costs 5 credits per page (100 subdomains by default). Returns each subdomain with its registrable domain, whether it is active, and its first-seen, last-seen and inactive-from dates, plus the total count. When there are more, the result has a nextPageToken: pass it as pageToken, with the same keyword or pattern, to get the next page. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • keywordstringBrand or name to find typo variants of inside subdomains: 3 to 63 letters, digits or hyphens, one label without a dot, not starting or ending with a hyphen. Exa
    • patternstringWildcard search instead of keyword: '*' matches any characters and '?' exactly one, at most 2 wildcards, at least 5 other characters including 3 in a row, 63 in
    • pageTokenstringnextPageToken from the previous result, to get the next page. Pass the same keyword or pattern with it.
    • fetchSizeintegerSubdomains per page, 1 to 10000. Default: 100
  • domainReputation1 param

    Assess how risky a domain is, live: a verdict (safe, low_risk, suspicious, malicious or unknown) with its confidence and severity, a trust score with the positive and negative signals behind it, DGA (algorithmically generated name) analysis, matches in threat-intelligence feeds, email security (SPF, DKIM, DMARC and mail servers), and a recommended action. Its DKIM check probes only a few selectors and can report DKIM missing when a key exists, for example a Microsoft 365 key published through a CNAME; to confirm DKIM, look up <selector>._domainkey.<domain> with dnsLookup. Use this to triage a suspicious domain from an email, a log or a domainDiscovery result before deciding whether to block it. For the domain's owner use liveWhoisLookup, for its certificate sslLookup, and for an IP address ipSecurity. Costs 5 credits. An unknown or unregistered domain still returns an assessment; lookups that failed are listed under errors and only leave out their signals. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • domainNamestringrequiredDomain to assess. Example: example.com (a URL also works)
  • sslLookup4 params

    Get the SSL/TLS certificate a domain currently serves, fetched live. Use this to check expiry dates, the issuer, covered hostnames (SANs) or key type, or to debug HTTPS errors. Set chain=true to include intermediate and root certificates when diagnosing trust-chain problems, and sslRaw=true only when you need the raw OpenSSL output, which is long. For DNS records use dnsLookup; for domain ownership use liveWhoisLookup; for an overall risk verdict on the domain use domainReputation. Costs 1 credit, plus 1 credit per 2 certificates with chain=true. Returns each certificate's subject (common name, organisation), issuer, validity dates, serial number, signature algorithm, key algorithm and size, and extensions: covered hostnames (SANs), key usages, issuer and OCSP URLs, and certificate policies. A domain with no certificate returns a "no data found" (HTTP 404) message. Behavior: read-only. Makes one request to the WhoisFreaks API for your WhoisFreaks account (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

    Show parameters
    • domainNamestringrequiredDomain name to retrieve SSL certificate for. Accepts: example.com | https://example.com | http://example.com
    • chainbooleanIf true, return the full certificate chain (end-user certificate through intermediate CA to root CA). Default: false
    • sslRawbooleanIf true, include the raw OpenSSL response in the output. Default: false
    • formatstringResponse format. Default: json
  • apiKeyUsage

    Show how much of the WhoisFreaks API key's allowance is used: pay-as-you-go credits bought and used, and the subscription's status, request limit, requests used and surcharge requests. Use this before a large job (a bulk lookup, many pages of reverse WHOIS or typosquatting results) to check there is enough left, or when a lookup fails with a plan or credit limit error. Returns the key (masked), its credits and its subscription usage; a part the account does not have is left out. Behavior: read-only. Reads the usage of your WhoisFreaks account's API key (identified by the WHOISFREAKS_API_KEY environment variable or, on the hosted server, by the API key sent with the request or the account connected with OAuth); it looks nothing up and changes nothing. If the key is invalid the result is a short message (HTTP 401) instead of data.

Checked by Serverdex with a plain initialize + tools/list call to mcp.whoisfreaks.com/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 15, 2026
Stars
0
Forks
0
Last push
Nov 15, 2026
License
MIT

Javaclaudednsdomain-intelligenceip-geolocationmcpmcp-servermodel-context-protocolsslthreat-intelligencewhois

From the README

WhoisFreaks MCP Server A Model Context Protocol (MCP) server that exposes the full WhoisFreaks API suite as AI-callable tools. Works with Claude Desktop, Cursor, Windsurf, VS Code, Continue, Zed, and any other MCP-compatible AI client. Three ways to use it — pick what fits your setup: Connect it to any MCP client via Streamable HTTP (/mcp endpoint, hosted or self-hosted) or stdio (local). Every user brings their own WhoisFreaks API key — the HTTP server stores no key of its own and uses the key sent with each request. Table of Contents 1. Tools Reference (22 tools) 2. Hosted Server (no install) • Signing In with OAuth 3. Quick Start • ⭐ Recommended — Docker • Build from Source 4. Prerequisites 5. Platform Integration • 1. Claude Desktop • 2. Cursor IDE • 3. Windsurf IDE • 4. VS Code + GitHub Copilot • 5. Continue.dev • 6. Zed Editor 6. Example Prompts 7. Troubleshooting Tools Reference WHOIS Tools IP & ASN WHOIS Tools DNS Tools IP Intelligence Tools Domain Tools SSL Tools Account Tools The API's key rotation endpoint has no tool on purpose: it would replace the key the MCP client uses and hand the new one to the AI. Rotate keys in the billing dashboard. The tools call the endpoints of the WhoisFreaks OpenAPI spec and cost the same credits as calling the API directly; the credit usage page lists them.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://mcp.whoisfreaks.com/mcp

Alternatives to WhoisFreaks

Best Search & Web servers →

The most-starred Search & Web servers in the index, with their live-check result.

ServerStarsLast pushLive check
Browser Use120,955Nov 2026Working
Scrapling MCP Server102,926Nov 2026Local / not checked
Chrome DevTools MCP58,028Nov 2026Local / not checked
Chrome DevTools MCP58,014Nov 2026Local / not checked
com.puter MCP Server44,182Nov 2026Needs sign-in

WhoisFreaks: questions people ask

Is WhoisFreaks a remote or a local MCP server?
According to its entry in the official MCP registry, WhoisFreaks ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does WhoisFreaks need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 19, 2026. Individual tools may still ask for a key when called.
Is WhoisFreaks still maintained?
Active: the repository's last commit 4 days ago. Last push Nov 15, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 15, 2026.
What tools does WhoisFreaks expose?
22 tools as listed by the server itself during the live check, including liveWhoisLookup, bulkWhoisLookup, whoisHistory, reverseWhoisLookup, ipWhoisLookup. The full list with parameters is in the Live check section above.
How do I add WhoisFreaks to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Search & Web →

Add the badge to your site

Show visitors that WhoisFreaks is listed here — it’s also the link we check for a free listing.

WhoisFreaks — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-whoisfreaks-whoisfreaks-mcp-server?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="WhoisFreaks — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![WhoisFreaks — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-whoisfreaks-whoisfreaks-mcp-server?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.