Domain History Contact OSINT - Previous Owner + WHOIS History MCP Server

by anshumanatrey Your server? Claim it

answering

Domain History Contact OSINT - Previous Owner + WHOIS History is answering right now. Last checked 11 min ago. Last commit 7 Oct 2026.

Domain History Lookup - WHOIS History + Past Owner Contacts

Uptime history 18 days of history · worst day 99%

18 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

326 ms

Response time

average over 24h

Stars

last commit 7 Oct 2026

Nothing serious here today

Today is the operative word: we check Domain History Contact OSINT - Previous Owner + WHOIS History every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add domain-history-contact-osint --transport http https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "domain-history-contact-osint": {
      "url": "https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint"
    }
  }
}

~/.codex/config.toml

[mcp_servers.domain-history-contact-osint]
url = "https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint"

.cursor/mcp.json

{
  "mcpServers": {
    "domain-history-contact-osint": {
      "url": "https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "domain-history-contact-osint": {
      "url": "https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint	streamable-http	needs key	297 ms	11 min ago

Alternatives to Domain History Contact OSINT - Previous Owner + WHOIS History

same job, measured the same way

OSINT

by robyroro

Domain and website investigations: batch recon, shared infrastructure, CT history and public lookups

661 installs/wk local only

DNS

by ofershap

MCP server for DNS lookups, reverse DNS, WHOIS, and domain checks — zero auth, zero config

49 installs/wk local only

Launch Record Lookup

by websitelaunches

Look up a domain's public Website Launches launch record, owner verification & trust context.

1 tools answering

Zillow Leads Property Data

by kmatata

MCP server for the zillow-leads-property-data actor: Zillow leads with agent contacts and history.

local only

Bulk WHOIS Domain Lookup

by fernandoguiraud16-coder

Bulk WHOIS/RDAP lookup: registrar, domain age, expiry date and availability.

answering

WhoisJSON

by whoisjson

WHOIS, DNS, SSL, and domain availability lookups for AI assistants

23 installs/wk local only

AgentPay Domain & Network Lookup

by noah-silver

Pay-per-call DNS, WHOIS/RDAP, IP and domain reports for agents. x402 USDC on Base or Algorand.

4 tools answering

Name.ai MCP Server

by name

Domain availability search, WHOIS lookup, TLD pricing and registry rules from name.ai. Read-only.

4 tools answering

Domain History Contact OSINT - Previous Owner + WHOIS History — questions

Answers built from our own checks of this server.

Why is there no tool list for Domain History Contact OSINT - Previous Owner + WHOIS History?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Domain History Contact OSINT - Previous Owner + WHOIS History working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 326 ms. The bar chart above shows every period we have measured.

How do I connect Domain History Contact OSINT - Previous Owner + WHOIS History?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does Domain History Contact OSINT - Previous Owner + WHOIS History need an API key?

Yes. Every time we knock, Domain History Contact OSINT - Previous Owner + WHOIS History answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Domain History Contact OSINT - Previous Owner + WHOIS History?

It answers our handshake in 326 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Domain History Contact OSINT - Previous Owner + WHOIS History open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.