Can I find all professional email addresses for a specific company?

Yes. Use `search_domain_emails` with a domain (e.g., 'stripe.com') or company name (e.g., 'Stripe') to retrieve all professional emails found for that organization. Each result includes the email, confidence score, position, and source URLs. Use `get_domain_email_count` to preview how many emails are available before using search credits.

Can I verify if an email address is valid before sending outreach?

Yes. The `verify_email_address` tool checks the validity and deliverability of any email address. It returns a status (deliverable, undeliverable, risky, unknown), confidence score, and details about the email server (MX records, SMTP check, accept-all detection). This prevents bounces and protects your sender reputation.

How does Hunter API authentication work?

Hunter uses an API Key passed as a query parameter (`?api_key=YOUR_KEY`) in all requests to `api.hunter.io/v2`. This differs from the typical Bearer token pattern. Your API key is available in the Hunter dashboard under Account > API. Free accounts include 25 searches and 50 verifications per month.

INSTANT PLUG AND PLAY

Hunter MCP Server for CrewAIGive CrewAI instant access to 12 tools to Create New Lead, Enrich Email Data, Find Person Email, and more

Name: Hunter
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Hunter through Vinkius, pass the Edge URL in the `mcps` parameter and every Hunter tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Use with Your AI Agent

Ask AI about this App Connector for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Hunter app connector for CrewAI is a standout in the Sales Automation category — giving your AI agent 12 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Hunter Specialist",
    goal="Help users interact with Hunter effectively",
    backstory=(
        "You are an expert at leveraging Hunter tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Hunter "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Hunter MCP Server

Connect your Hunter account to any AI agent and power your email prospecting through natural conversation.

When paired with CrewAI, Hunter becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Hunter tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Domain Search — Find all professional email addresses associated with a domain or company name
Email Finder — Discover the most likely email address for a specific person by name and company
Email Verification — Check the validity and deliverability of any email address with confidence scores
Email Count — Check how many email addresses are available for a domain before searching
Contact Enrichment — Retrieve all available professional data (title, company, social profiles) for an email address
Lead Management — Create, list, update, and delete leads in your Hunter CRM with lead list organization
Account Monitoring — Track remaining API credits and account usage

The Hunter MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 12 Hunter tools available for CrewAI

When CrewAI connects to Hunter through Vinkius, your AI agent gets direct access to every tool listed below — spanning email-finder, domain-search, email-verification, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

create_new_lead

Save lead to CRM

enrich_email_data

Get contact intel

find_person_email

Find personal email

get_account_usage

Check credits

get_domain_email_count

Check email availability

get_lead_details

Get lead info

list_lead_folders

List lead lists

list_saved_leads

List lead profiles

remove_lead

Delete lead record

search_domain_emails

Find emails for domain

update_lead_info

Modify lead data

verify_email_address

Check deliverability

Connect Hunter to CrewAI via MCP

Follow these steps to wire Hunter into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Hunter

Why Use CrewAI with the Hunter MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Hunter through the Model Context Protocol.

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 `mcps` parameter 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

Hunter + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Hunter MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Hunter for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Hunter, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Hunter tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Hunter against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Hunter in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Hunter immediately.

"Find all emails at stripe.com and verify the CTO's email address."

"Find the email for Sarah Chen at Acme Corp and enrich her contact data."

"Check my Hunter account credits and list all saved leads."

Troubleshooting Hunter MCP Server with CrewAI

Common issues when connecting Hunter to CrewAI through the Vinkius, and how to resolve them.

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.

Hunter + CrewAI FAQ

Common questions about integrating Hunter MCP Server with CrewAI.

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.