Bring Whois
to LlamaIndex
Learn how to connect IP2WHOIS to LlamaIndex 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 LlamaIndex?
LlamaIndex agents combine IP2WHOIS tool responses with indexed documents for comprehensive, grounded answers. Connect 10 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine IP2WHOIS tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain IP2WHOIS tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query IP2WHOIS, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what IP2WHOIS tools were called, what data was returned, and how it influenced the final answer
IP2WHOIS in LlamaIndex
IP2WHOIS and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect IP2WHOIS to LlamaIndex 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 LlamaIndex
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 LlamaIndex 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 LlamaIndex
Every tool call from LlamaIndex 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 LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query IP2WHOIS tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
