Bring Whois
to Cursor
Learn how to connect IP2WHOIS to Cursor 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 Cursor?
Cursor's Agent mode turns IP2WHOIS into an in-editor superpower. Ask Cursor to generate code using live data from IP2WHOIS and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
IP2WHOIS in Cursor
IP2WHOIS and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect IP2WHOIS to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.