What it does
WHOIS, DNS, IP geolocation, SSL and domain intelligence from the WhoisFreaks API.
- Connects 在云端运行
- Account or key Needs Authorization
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-13 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 5/5 项(仅展示,不用于排序)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 WhoisFreaks。按照 https://mcp.popnx.com/i/whoisfreaks-mcp-server.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.whoisfreaks.com) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 WhoisFreaks 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称WhoisFreaksRemote MCP server URL · 地址https://mcp.whoisfreaks.com/mcp在 Request headers 下添加这个名称和值
Header 名称Authorization值Bearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsWhoisFreaks
试一试
用 WhoisFreaks 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 WhoisFreaks,或回答中出现 WhoisFreaks 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 WhoisFreaks
WhoisFreaks 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
你可以改用这些方式
A · 使用能连接 WhoisFreaks 的应用
- 需要 WhoisFreaks 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
- 需要 WhoisFreaks 的密钥(在开发者网站创建)
- 需要 WhoisFreaks 的密钥(在开发者网站创建)
- 需要 WhoisFreaks 的密钥(在开发者网站创建)
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
可连接 Claude Code · 约 5 分钟
需要 WhoisFreaks 的密钥(在开发者网站创建)
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user whoisfreaks https://mcp.whoisfreaks.com/mcp --header 'Authorization: Bearer {api_key}'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude Code 中输入 /mcp
应能看到 WhoisFreaks 在列表中并显示已连接
试一试
用 WhoisFreaks 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 WhoisFreaks,或回答中出现 WhoisFreaks 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 WhoisFreaks 的密钥(在开发者网站创建)
填写你的密钥
在 WhoisFreaks 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 WhoisFreaks 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 WhoisFreaks,或回答中出现 WhoisFreaks 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 WhoisFreaks 的密钥(在开发者网站创建)
填写你的密钥
在 WhoisFreaks 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 WhoisFreaks 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 WhoisFreaks,或回答中出现 WhoisFreaks 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user whoisfreaks https://mcp.whoisfreaks.com/mcp --header 'Authorization: Bearer {api_key}'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"whoisfreaks": {
"url": "https://mcp.whoisfreaks.com/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"whoisfreaks": {
"type": "http",
"url": "https://mcp.whoisfreaks.com/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}需要你填写的值
- 您的 WhoisFreaks API 密钥,作为 bearer 令牌使用。可在 https://billing.whoisfreaks.com/signup 免费注册获取
查看英文原文
Your WhoisFreaks API key as a bearer token. Get one free at https://billing.whoisfreaks.com/signup
说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
它能做什么
工具名称和描述与服务器在 2026年11月14日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
liveWhoisLookupGet 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
bulkWhoisLookupGet 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
whoisHistoryGet 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 cu
reverseWhoisLookupFind 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
ipWhoisLookupGet 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, T
asnWhoisLookupGet 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 announc
dnsLookupResolve 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 an
bulkDnsLookupResolve 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 domainName
dnsHistoryGet 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
reverseDnsLookupFind 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. S
ipGeolocationLook 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 m
bulkIpGeolocationLook 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
ipSecurityCheck 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,
bulkIpSecurityCheck 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
domainAvailabilityCheck 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
bulkDomainAvailabilityCheck 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 cand
subdomainLookupList 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
domainDiscoveryFind 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. Provi
subdomainTyposquattingFind 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 domai
domainReputationAssess 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,
sslLookupGet 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
apiKeyUsageShow 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 result
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 WhoisFreaks 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于3天前
- ✓ 通过
有许可证
使用 MIT
- ✓ 通过
端点有响应
在 109 毫秒内响应(HTTP 200)
- – 不适用
使用 OAuth 登录
无需登录
- ✓ 通过
工具描述中没有隐藏指令
已读取 22 个工具描述,未发现针对 AI 的隐藏指令
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/whoisfreaks-mcp-server)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6103 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 6103 个服务器的 88% 更新
- 基础检查结果等于或优于此分类中其他 6103 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
WhoisFreaks 安全吗?
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:Authorization
它在我的电脑上运行还是在云端?
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
它还在维护吗?
GitHub 仓库最后更新于3天前,最新版本(2.1.0)于5天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 WhoisFreaks | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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:
| Method | Requires | Best for | |
|---|---|---|---|
| ⭐ Easiest | Hosted server | Just your API key | Everyone — nothing to install |
| Docker (pre-built image) | Docker | Running it on your own machine or VM | |
| Build from source | Java 17 + Maven | Contributors / custom builds |
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
- Tools Reference (22 tools)
- Hosted Server (no install)
- Signing In with OAuth
- Quick Start
- ⭐ Recommended — Docker
- Build from Source
- Prerequisites
- Platform Integration
- 1. Claude Desktop
- 2. Cursor IDE
- 3. Windsurf IDE
- 4. VS Code + GitHub Copilot
- 5. Continue.dev
- 6. Zed Editor
- Example Prompts
- Troubleshooting
Tools Reference
WHOIS Tools
| Tool | Description |
|---|---|
liveWhoisLookup | Real-time WHOIS data for any domain — registrar, registrant, dates, nameservers |
bulkWhoisLookup | Real-time WHOIS data for up to 100 domains in one request |
whoisHistory | Complete ownership history timeline for a domain |
reverseWhoisLookup | Find all domains registered by an email address, owner name or company, or whose name contains a keyword |
IP & ASN WHOIS Tools
| Tool | Description |
|---|---|
ipWhoisLookup | WHOIS registration data for any IPv4 or IPv6 address |
asnWhoisLookup | WHOIS data for an Autonomous System Number (e.g. AS15169) |
DNS Tools
| Tool | Description |
|---|---|
dnsLookup | Live DNS records — A, AAAA, MX, NS, CNAME, SOA, TXT, SPF, or all — and PTR records for an IP |
bulkDnsLookup | Live DNS records for up to 100 domains and 100 IPs in one request |
dnsHistory | Historical DNS records with full change timeline |
reverseDnsLookup | Find all domains pointing to a given IP or range, mail server or nameserver |
IP Intelligence Tools
| Tool | Description |
|---|---|
ipGeolocation | Country, city, region, ISP, and coordinates for any IP address |
bulkIpGeolocation | Geolocation for up to 100 IP addresses in one request |
ipSecurity | IP reputation: VPN, proxy, Tor exit node, relay, bot, spam and known-attacker signals |
bulkIpSecurity | IP reputation for up to 100 IP addresses in one request |
Domain Tools
| Tool | Description |
|---|---|
domainAvailability | Check if a domain is available to register, with optional suggestions |
bulkDomainAvailability | Check up to 100 domains, or one name across up to 100 extensions (TLDs) |
subdomainLookup | Enumerate all known subdomains for a domain, with status and date filters |
domainDiscovery | Find registered domains that are typo variants of a brand (typosquatting), by keyword or wildcard pattern |
subdomainTyposquatting | Find subdomains on any domain that contain a typo variant of a brand, such as login.paypa1.example.com |
domainReputation | Risk verdict, trust score, DGA analysis, threat-feed matches and email security for a domain |
SSL Tools
| Tool | Description |
|---|---|
sslLookup | SSL/TLS certificate details — issuer, expiry, SANs, chain, and raw output |
Account Tools
| Tool | Description |
|---|---|
apiKeyUsage | Credits and subscription requests used by your API key (costs nothing) |
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. Bulk tools cost credits for each item.
Hosted Server (no install)
Point any MCP client that supports remote servers at:
https://mcp.whoisfreaks.com
(https://mcp.whoisfreaks.com/mcp is the same endpoint, for clients or configs that expect that path)
and send your WhoisFreaks API key (get one free) in one of these ways:
| Method | Example | Use with |
|---|---|---|
Authorization header | Authorization: Bearer YOUR_API_KEY | Claude Code, Cursor, VS Code, Windsurf, Continue |
X-API-Key header | X-API-Key: YOUR_API_KEY | Any client that supports custom headers |
| Query parameter | https://mcp.whoisfreaks.com/?apiKey=YOUR_API_KEY | Clients without custom headers (claude.ai / Claude Desktop custom connectors) |
Prefer a header when your client supports one — URLs with keys can end up in logs and history.
Claude Code
claude mcp add --transport http whoisfreaks https://mcp.whoisfreaks.com \
--header "Authorization: Bearer YOUR_API_KEY"
claude.ai / Claude Desktop — Settings → Connectors → Add custom connector, URL:
https://mcp.whoisfreaks.com/?apiKey=YOUR_API_KEY
Cursor (~/.cursor/mcp.json), Windsurf, and other JSON-configured clients:
{
"mcpServers": { "whoisfreaks": { "url": "https://mcp.whoisfreaks.com", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }
VS Code (.vscode/mcp.json):
{
"servers": { "whoisfreaks": { "type": "http", "url": "https://mcp.whoisfreaks.com", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }
Without a key the server still connects and lists its tools, but every tool call returns an error explaining how to add one. API usage is billed to the key you send.
Signing In with OAuth
ChatGPT and Codex connect to MCP servers only with OAuth, so the WhoisFreaks plugin for them signs users in to their WhoisFreaks account instead of sending an API key. The hosted server does both at the same address: set these variables and it also takes OAuth access tokens, while API keys keep working exactly as above.
| Variable | Example | Description |
|---|---|---|
OAUTH_ISSUER | https://auth.whoisfreaks.com | Turns OAuth sign-in on: the authorization server, which signs users in with their WhoisFreaks account |
MCP_RESOURCE | https://mcp.whoisfreaks.com | This server's address, without a path. Access tokens must name it (or it plus /mcp) as their audience |
BILLING_URL | https://billing-backend.whoisfreaks.com | Where the server trades access tokens for API keys |
BILLING_SERVER_TOKEN | — | The shared secret for that trade (billing's oauth.mcp-server-token) |
OAUTH_JWKS_URI | OAUTH_ISSUER/oauth2/jwks (default) | The authorization server's signing keys |
With OAUTH_ISSUER set, the other three are required: the server won't start half set up. How it tells requests apart:
- An API key (
Authorization: Bearer,X-API-Keyor?apiKey=), or no credentials at all: handled exactly as without OAuth. In particular, a request without credentials is never answered with a 401, so MCP clients that send keys never start an OAuth sign-in by mistake. - An access token (
Authorization: Bearerwith a JWT, which an API key never is): it must be RS256, signed with one of the issuer's keys, issued for this server, not expired, with thelookupsscope. It is traded for the account's API key at billing, cached for up to a minute and never past the token's expiry. Tokens never contain the key, and the key is never logged. - An access token that can't be used (expired, invalid, or no longer accepted by billing because the user disconnected, changed their password or signed out of all devices) gets
401withWWW-Authenticate: Bearer error="invalid_token", resource_metadata="…", so the app refreshes it or asks the user to connect again. A token without thelookupsscope gets403. If the account can't run lookups (inactive, or no active key), tools return an error explaining why instead.
Apps find where to sign in at GET /.well-known/oauth-protected-resource (and /.well-known/oauth-protected-resource/mcp, for the /mcp URL). A key restricted to listed IPs only works here if this server's address is on its list.
deploy/docker-compose.yml passes the variables through from the environment or a .env file next to it. ansible/ writes them when OAUTH_ISSUER is set in its .env (ansible/README.md, section 9).
Quick Start
⭐ Recommended — Docker
No Java or Maven required. Pull the pre-built image directly from Docker Hub and run.
The container runs the same multi-user HTTP server as the hosted one: it needs no API key of its own — clients send theirs with each request (see Hosted Server for the ways to send it). Get a free key at billing.whoisfreaks.com/signup.
Option 1 — Direct docker run (simplest)
docker run -d \
--name whoisfreaks-mcp \ --restart unless-stopped \ -p 3100:3100 \ whoisfreaks/mcp-server:latest
The MCP server is now live at `http://localhost:3100/mcp`.
Option 2 — Docker Compose (recommended for production / VM)
Create a docker-compose.yml:
services:
whoisfreaks-mcp: image: whoisfreaks/mcp-server:latest container_name: whoisfreaks-mcp restart: unless-stopped ports:
- "3100:3100"
Start it:
docker compose up -d
Serving it publicly (HTTPS)
Put a reverse proxy with TLS in front of port 3100. Caddy example (Caddyfile), which obtains a certificate automatically:
mcp.example.com {
reverse_proxy localhost:3100 }
Nginx example:
location / {
proxy_pass http://127.0.0.1:3100; proxy_http_version 1.1; proxy_set_header Host $host; proxy_buffering off; # stream responses as they are produced proxy_read_timeout 300s; # some WHOIS lookups are slow }
The server is stateless (no MCP sessions), so you can run several containers behind a load balancer without sticky sessions.
To set up a machine and deploy to it without Docker (nginx, HTTPS, rate limiting, rollback), see ansible/.
Verify Docker is working
# Container should show as "Up"
docker ps
Health check
curl http://localhost:3100/health
→ {"status":"ok"}
List all 22 registered tools (any key works for listing; tool calls need a valid one)
curl -s http://localhost:3100/mcp \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -H "Authorization: Bearer your-api-key-here" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Use with Claude Desktop (Docker stdio mode)
To run the server locally over stdio instead of HTTP, override the Docker entrypoint and pass your key as an environment variable:
{
"mcpServers": { "whoisfreaks": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "WHOISFREAKS_API_KEY=your-api-key-here", "--