Bring Whois
to CrewAI
Learn how to connect IP2WHOIS to CrewAI 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 CrewAI?
When paired with CrewAI, IP2WHOIS becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call IP2WHOIS tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
IP2WHOIS in CrewAI
IP2WHOIS and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect IP2WHOIS to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.