Bring Lead Enrichment
to CrewAI
Learn how to connect CUFinder to CrewAI and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the CUFinder MCP Server?
Connect your CUFinder business intelligence account to any AI agent and simplify how you discover professional domains, enrich company metadata, and identify decision makers through natural conversation.
What you can do
- Domain Discovery — Find the primary web domain for any company using only its trade name via AI.
- Company Intelligence — Retrieve detailed metadata including industry, location, and estimated annual revenue for specific domains.
- Employee Prospecting — List known employees and key decision makers associated with a company domain.
- LinkedIn Enrichment — Fetch detailed contact info and professional data from specific LinkedIn profile URLs.
- Lead Qualification — Verify company size and financial standing to prioritize your sales outreach.
- Data Accuracy — Enhance your CRM records with verified real-time data directly from the agent.
How it works
1. Subscribe to this server
2. Enter your CUFinder API Key (found in your account dashboard)
3. Start enriching your sales pipeline from Claude, Cursor, or any MCP client
Who is this for?
- Sales & SDR Teams — quickly find company domains and decision maker lists via simple AI commands.
- Marketing & Growth — enrich lead lists with revenue and industry data directly from the workspace.
- Business Analysts — perform quick competitive intelligence and market research via the AI assistant.
Built-in capabilities (13)
Bulk enrich
Verify connectivity
Enrich LinkedIn profile
Find company domain
Find email address
Find employees
Find phone number
Get account info
Get company info
Get company revenue
Get social profiles
Get tech stack
Verify email
Why CrewAI?
When paired with CrewAI, CUFinder becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call CUFinder 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
CUFinder in CrewAI
CUFinder and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect CUFinder 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 CUFinder in CrewAI
The CUFinder 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 13 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
CUFinder for CrewAI
Every tool call from CrewAI to the CUFinder MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I find the official website for a company via AI?
Yes! Use the find_company_domain tool and provide the company name. Your agent will return the primary web domain registered for that entity.
How do I see the estimated revenue for a specific company?
Run the get_company_revenue query and provide the domain. The agent will retrieve the estimated annual revenue range from CUFinder's database.
Is it possible to list employees for a domain via AI?
Absolutely. Use the find_company_employees tool. The agent will retrieve a list of known employees and decision makers associated with that specific company domain.
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.