Bring Whois
to Claude Desktop
Learn how to connect IP2WHOIS to Claude Desktop and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the IP2WHOIS MCP Server?
Connect your IP2WHOIS account to any AI agent and access comprehensive domain intelligence through natural conversation.
What you can do
- WHOIS Lookup — Get complete registration records for any domain including dates, registrar, and contacts.
- Domain Age — Calculate how old a domain is in days and years.
- Expiry Monitoring — Check when domains expire and how many days remain.
- Registrar & Nameservers — Extract registrar details and DNS nameserver configurations.
- Availability Check — Determine if a domain is available for registration.
- Reverse IP — Find all domains hosted on a specific IP address.
- Bulk Lookup — Query up to 10 domains in a single operation.
How it works
1. Subscribe to this server
2. Enter your IP2WHOIS API key (free tier: 500 queries/month)
3. Start querying domains from Claude, Cursor, or any MCP client
Who is this for?
- Security Researchers — investigate domain ownership and infrastructure.
- Domain Investors — monitor expiry dates and check availability.
- IT Administrators — audit DNS configurations and shared hosting environments.
Built-in capabilities (10)
Returns key registration details for each domain. WHOIS lookup for multiple domains at once
Check the age of a domain
Check if a domain is available for registration
Useful for renewal monitoring. Check when a domain expires
com to confirm valid authentication. Verify IP2WHOIS API connectivity
Note: many domains use privacy protection. Get registrant and admin contact info for a domain
Get nameservers for a domain
Get registrar and status info for a domain
Full WHOIS lookup for a domain
Useful for shared hosting analysis. Find all domains hosted on a specific IP address
Why Claude Desktop?
Claude Desktop is the definitive way to connect IP2WHOIS to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
IP2WHOIS in Claude Desktop
IP2WHOIS and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect IP2WHOIS to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for IP2WHOIS in Claude Desktop
The IP2WHOIS MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
IP2WHOIS for Claude Desktop
Every tool call from Claude Desktop to the IP2WHOIS MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check if a domain is available for registration?
Yes! Use check_domain_availability with the domain name. It analyzes the WHOIS record to determine if the domain appears unregistered.
How many domains can I look up at once?
Use bulk_whois_lookup with a comma-separated list of up to 10 domains to get key registration details for each one in a single request.
Can I find which domains are hosted on a specific server?
Yes! Use lookup_hosted_domains with an IPv4 or IPv6 address to perform a reverse IP lookup and discover all domains on that server.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.