# WhoisFreaks (remote · mcp.whoisfreaks.com)

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

- Trust score: 72/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.whoisfreaks.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/whoisfreaks-whoisfreaks-mcp-server/mcp.md), [page](https://verifymcp.io/servers/whoisfreaks-whoisfreaks-mcp-server/mcp)

## Channel facts

- Endpoint: `https://mcp.whoisfreaks.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 8726 tokens (~396/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the WhoisFreaks MCP server?

WhoisFreaks is a hosted endpoint at https://mcp.whoisfreaks.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http whoisfreaks-whoisfreaks-mcp-server 'https://mcp.whoisfreaks.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "whoisfreaks-whoisfreaks-mcp-server": {
      "url": "https://mcp.whoisfreaks.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "whoisfreaks-whoisfreaks-mcp-server": {
      "type": "http",
      "url": "https://mcp.whoisfreaks.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.whoisfreaks-whoisfreaks-mcp-server]
url = "https://mcp.whoisfreaks.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "whoisfreaks-whoisfreaks-mcp-server": {
      "type": "remote",
      "url": "https://mcp.whoisfreaks.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add whoisfreaks-whoisfreaks-mcp-server --url 'https://mcp.whoisfreaks.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  whoisfreaks-whoisfreaks-mcp-server:
    url: "https://mcp.whoisfreaks.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "whoisfreaks-whoisfreaks-mcp-server": {
      "Transport": "http",
      "Url": "https://mcp.whoisfreaks.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add whoisfreaks-whoisfreaks-mcp-server -t streamable-http -u 'https://mcp.whoisfreaks.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "whoisfreaks-whoisfreaks-mcp-server": {
      "type": "http",
      "url": "https://mcp.whoisfreaks.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 70, +1)

- [security] Tool “apiKeyUsage” rewrote its description, which is the text the model reads
- [security] Tool “asnWhoisLookup” rewrote its description, which is the text the model reads
- [security] Tool “bulkDnsLookup” rewrote its description, which is the text the model reads
- [security] Tool “bulkDomainAvailability” rewrote its description, which is the text the model reads
- [security] Tool “bulkIpGeolocation” rewrote its description, which is the text the model reads
- [security] Tool “bulkIpSecurity” rewrote its description, which is the text the model reads
- [security] Tool “bulkWhoisLookup” rewrote its description, which is the text the model reads
- [security] Tool “dnsHistory” rewrote its description, which is the text the model reads
- [security] Tool “dnsLookup” rewrote its description, which is the text the model reads
- [security] Tool “domainAvailability” rewrote its description, which is the text the model reads
- [security] Tool “domainDiscovery” rewrote its description, which is the text the model reads
- [security] Tool “domainReputation” rewrote its description, which is the text the model reads
- [security] Tool “ipGeolocation” rewrote its description, which is the text the model reads
- [security] Tool “ipSecurity” rewrote its description, which is the text the model reads
- [security] Tool “ipWhoisLookup” rewrote its description, which is the text the model reads
- [security] Tool “liveWhoisLookup” rewrote its description, which is the text the model reads
- [security] Tool “reverseDnsLookup” rewrote its description, which is the text the model reads
- [security] Tool “reverseWhoisLookup” rewrote its description, which is the text the model reads
- [security] Tool “sslLookup” rewrote its description, which is the text the model reads
- [security] Tool “subdomainLookup” rewrote its description, which is the text the model reads
- [security] Tool “subdomainTyposquatting” rewrote its description, which is the text the model reads
- [security] Tool “whoisHistory” rewrote its description, which is the text the model reads

### 2026-11-16 (score 69, 0)

- [security] Tool “dnsLookup” rewrote its description, which is the text the model reads
- [security] Tool “domainAvailability” rewrote its description, which is the text the model reads
- [security] Tool “domainReputation” rewrote its description, which is the text the model reads

### 2026-11-15 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 68)

First indexed and scored.

## MCP tools (22)

### `liveWhoisLookup` (~370 tokens)

Live WHOIS lookup

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).

Input parameters:

- `domainName` (string, required): Domain name to look up. Accepts: example.com | https://example.com | http://example.com
- `format` (string): Response format. Default: json

### `bulkWhoisLookup` (~320 tokens)

Bulk WHOIS lookup

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).

Input parameters:

- `domainNames` (array, required): Domain names to look up, at most 100. Example: ["whoisfreaks.com", "jfreaks.com"]
- `format` (string): Response format. Default: json

### `whoisHistory` (~313 tokens)

WHOIS history

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).

Input parameters:

- `domainName` (string, required): Domain name to look up history for. Examples: whoisfreaks.com | google.com
- `format` (string): Response format. Default: json

### `reverseWhoisLookup` (~552 tokens)

Reverse WHOIS search

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).

Input parameters:

- `company` (string): Search by company/organization name, matched as a phrase unless exact=true. Example: Alphabet Inc
- `email` (string): Search by registrant email address, exact or regex match. Example: admin@example.com
- `exact` (boolean): false (the default): keyword matches every domain that contains it, and owner and company match as a phrase. true: match the value exactly.
- `format` (string): Response format. Default: json
- `keyword` (string): Search by text in the domain name. With exact=false (the default) it matches every domain whose name contains it. Example: google
- `mode` (string): '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 registrant's name, email and company, 100…
- `owner` (string): Search by registrant/owner name, matched as a phrase unless exact=true. Example: John Doe
- `page` (integer): Page number for paginated results. Default: 1

### `ipWhoisLookup` (~334 tokens)

IP WHOIS lookup

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).

Input parameters:

- `format` (string): Response format. Default: json
- `ip` (string, required): IPv4 or IPv6 address to look up. Examples: 8.8.8.8 | 2001:4860:4860::8888

### `asnWhoisLookup` (~297 tokens)

ASN WHOIS lookup

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).

Input parameters:

- `asn` (string, required): Autonomous System Number to look up. Accepts 'AS15169' or plain '15169'.
- `format` (string): Response format. Default: json

### `dnsLookup` (~633 tokens)

DNS lookup

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).

Input parameters:

- `cnameDepth` (integer): How many CNAME hops to follow before collecting records, 0 to 4. Default: 0
- `domainName` (string): Domain name to query DNS records for. Example: google.com. Optional when ipAddress is given.
- `format` (string): Response format. Default: json
- `ipAddress` (string): IP address for a reverse (PTR) lookup. Example: 8.8.8.8. Pass it instead of, or together with, domainName.
- `relativeRecords` (boolean): true (the default): include the records of CNAME targets. false: only the records on the queried name.
- `type` (string): Record 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.

### `bulkDnsLookup` (~467 tokens)

Bulk DNS lookup

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).

Input parameters:

- `cnameDepth` (integer): How many CNAME hops to follow before collecting records, 0 to 4. Default: 0
- `domainNames` (array): Domain names to resolve, at most 100. Example: ["whoisfreaks.com", "jfreaks.com"]
- `format` (string): Response format. Default: json
- `ipAddresses` (array): IP addresses for reverse (PTR) lookups, at most 100. Example: ["1.1.1.1", "8.8.8.8"]
- `type` (string): Record 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.

### `dnsHistory` (~357 tokens)

DNS history

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).

Input parameters:

- `domainName` (string, required): Domain name to retrieve historical DNS records for. Example: whoisfreaks.com
- `format` (string): Response format. Default: json
- `page` (integer): Page number for paginated results. Default: 1
- `type` (string): Record 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.

### `reverseDnsLookup` (~551 tokens)

Reverse DNS search

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).

Input parameters:

- `exact` (boolean): false (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 or range.
- `format` (string): Response format. Default: json
- `page` (integer): Page number for paginated results. Default: 1
- `sort` (string): Sort the results by sortBy, ascending or descending. Omit for unsorted results.
- `sortBy` (string): Date that sort orders by. Only used together with sort. Default: lastSeen
- `type` (string): One DNS record type to search within. Default: a
- `value` (string, required): The 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 text for TXT and SOA. With exact=false…

### `ipGeolocation` (~336 tokens)

IP geolocation

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).

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address to geolocate. Examples: 8.8.8.8 | 2606:4700:4700::1111

### `bulkIpGeolocation` (~269 tokens)

Bulk IP geolocation

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).

Input parameters:

- `ips` (array, required): IPv4 or IPv6 addresses to geolocate, at most 100. Example: ["1.1.1.1", "8.8.8.8"]

### `ipSecurity` (~351 tokens)

IP reputation check

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).

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address to run security analysis on. Examples: 1.1.1.1 | 185.220.101.0

### `bulkIpSecurity` (~300 tokens)

Bulk IP reputation check

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).

Input parameters:

- `ips` (array, required): IPv4 or IPv6 addresses to check, at most 100. Example: ["1.1.1.1", "185.220.101.45"]

### `domainAvailability` (~378 tokens)

Domain availability check

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).

Input parameters:

- `count` (integer): Number of suggestions to return when suggestions=true, 5 to 100. Default: 5
- `domain` (string, required): Domain name to check availability for. Example: whoisfreaks.com
- `format` (string): Response format. Default: json
- `suggestions` (boolean): If true, also return alternative domain names with other extensions and whether each is available. Default: false

### `bulkDomainAvailability` (~416 tokens)

Bulk domain availability check

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).

Input parameters:

- `domain` (string): The name to check across the extensions in tlds. Example: whoisfreaks.com. Use together with tlds.
- `domainNames` (array): Full domain names to check, at most 100. Example: ["whoisfreaks.io", "jfreaks.pk"]. Leave out when you pass domain and tlds.
- `format` (string): Response format. Default: json
- `tlds` (array): Extensions (TLDs) to check the domain against, without the leading dot, at most 100. Example: ["io", "dev", "ai"]

### `subdomainLookup` (~486 tokens)

Subdomain lookup

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).

Input parameters:

- `after` (string): Return 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
- `before` (string): Return subdomains first seen before this date (ISO format: YYYY-MM-DD). Must not be in the future. Example: 2024-01-01
- `domain` (string, required): Domain to find subdomains for. Example: whoisfreaks.com. A subdomain such as api.whoisfreaks.com returns the hosts beneath it.
- `format` (string): Response format. Default: json
- `page` (integer): Page number for paginated results. Default: 1
- `status` (string): Filter by subdomain status. Omit to return both active and inactive.

### `domainDiscovery` (~499 tokens)

Domain typosquatting search

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).

Input parameters:

- `fetchSize` (integer): Domains per page, 1 to 10000. Default: 100
- `keyword` (string): Brand or name to find typo variants of: 3 to 63 letters, digits or hyphens, one label without a dot. Example: paypal (not paypal.com)
- `pageToken` (string): nextPageToken from the previous result, to get the next page. Pass the same keyword or pattern with it.
- `pattern` (string): Wildcard search instead of keyword: '*' matches any characters, at most 3 asterisks, at least 5 other characters and 63 in total. Example: *paypa*

### `subdomainTyposquatting` (~490 tokens)

Subdomain typosquatting search

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).

Input parameters:

- `fetchSize` (integer): Subdomains per page, 1 to 10000. Default: 100
- `keyword` (string): Brand 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. Example: paypal
- `pageToken` (string): nextPageToken from the previous result, to get the next page. Pass the same keyword or pattern with it.
- `pattern` (string): Wildcard 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 total. Example: payp?l*

### `domainReputation` (~380 tokens)

Domain reputation check

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).

Input parameters:

- `domainName` (string, required): Domain to assess. Example: example.com (a URL also works)

### `sslLookup` (~426 tokens)

SSL certificate lookup

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).

Input parameters:

- `chain` (boolean): If true, return the full certificate chain (end-user certificate through intermediate CA to root CA). Default: false
- `domainName` (string, required): Domain name to retrieve SSL certificate for. Accepts: example.com | https://example.com | http://example.com
- `format` (string): Response format. Default: json
- `sslRaw` (boolean): If true, include the raw OpenSSL response in the output. Default: false

### `apiKeyUsage` (~201 tokens)

API key usage

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/whoisfreaks-whoisfreaks-mcp-server/mcp#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 70
- 2026-11-17: 70
- 2026-11-16: 69
- 2026-11-15: 69
- 2026-11-14: 68
- 2026-11-13: 68

## Common questions

### What is the WhoisFreaks MCP server?

WhoisFreaks is an MCP server listed in the public MCP registry as io.github.WhoisFreaks/whoisfreaks-mcp-server. WHOIS, DNS, IP geolocation, SSL and domain intelligence from the WhoisFreaks API. This page covers its hosted endpoint (https://mcp.whoisfreaks.com/mcp).

### Is the WhoisFreaks MCP server safe to use?

WhoisFreaks scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the WhoisFreaks MCP server expose?

WhoisFreaks exposes 22 tools: liveWhoisLookup, bulkWhoisLookup, whoisHistory, reverseWhoisLookup, ipWhoisLookup, and 17 more. Their descriptions and schemas cost roughly 8,726 tokens of context every time the server is loaded.

### Does the WhoisFreaks MCP server require authentication?

No. We connected to WhoisFreaks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the WhoisFreaks MCP server still maintained?

WhoisFreaks is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the WhoisFreaks MCP server?

VerifyMCP ran 13 checks on WhoisFreaks, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.whoisfreaks.com/mcp
- Authorisation metadata: https://mcp.whoisfreaks.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/WhoisFreaks/whoisfreaks-mcp-server
- Website: https://whoisfreaks.com/integrations/third-party/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/whoisfreaks-whoisfreaks-mcp-server/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/whoisfreaks-whoisfreaks-mcp-server/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/whoisfreaks-whoisfreaks-mcp-server/mcp.json
- HTML version of this page: https://verifymcp.io/servers/whoisfreaks-whoisfreaks-mcp-server/mcp
