How does Findymail ensure the accuracy of the found emails?

Findymail uses a proprietary verification engine that checks the deliverability of B2B emails in real-time. By using the 'verify_email' tool, you can double-check any address to ensure your bounce rate stays below 1%.

Can I search for leads using natural language like 'Founders in San Francisco'?

Yes! The 'search_leads' tool uses the Intellimatch engine, allowing you to discover companies and contacts based on conversational queries. It's like having a lead researcher built into your AI agent.

What happens if a phone number or email cannot be found?

If Findymail cannot locate a verified contact, the tool will return a null or empty status. Findymail only charges credits for successful finds, ensuring you only pay for data you can actually use.

Findymail MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: Findymail
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Findymail Specialist",
    goal="Help users interact with Findymail effectively",
    backstory=(
        "You are an expert at leveraging Findymail 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 Findymail "
        "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 Findymail MCP Server

Connect your Findymail account to any AI agent and supercharge your sales prospecting and data enrichment workflows through the power of the Model Context Protocol (MCP). Findymail is designed for high-growth sales teams that need accurate, verified contact data without the manual grind of searching through LinkedIn or guessing email patterns.

When paired with CrewAI, Findymail becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Findymail 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

Precision Email Finding — Instantly retrieve verified B2B emails by providing a person's name and their company domain or name. No more guessing; get data that actually delivers.
Real-time Email Verification — Protect your sender reputation by verifying any email address before it hits your outreach sequence. Our verification tool checks for deliverability in seconds.
Direct Phone Discovery — Scale your cold calling efforts by fetching direct phone numbers directly from LinkedIn profiles using our specialized phone finder tool.
Deep Company Enrichment — Transform a simple domain or LinkedIn URL into a full company profile, including industry data, size, and social identifiers.
Intellimatch Lead Generation — Use natural language to discover new leads. Simply ask your agent to 'Find SaaS founders in the US' or 'Get me marketing heads in London', and let Findymail do the heavy lifting.
List & Contact Management — Organically manage your prospecting lists and retrieve specific contact details to keep your CRM updated and your outreach personalized.
Credit Monitoring — Keep a pulse on your API usage with built-in tools to check your remaining credits and usage summaries directly from your AI conversation.

The Findymail 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.

How to Connect Findymail to CrewAI via MCP

Follow these steps to integrate the Findymail MCP Server with CrewAI.

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 Findymail

Why Use CrewAI with the Findymail MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Findymail 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

Findymail + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Findymail 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 Findymail, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Findymail 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 Findymail against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Findymail MCP Tools for CrewAI (12)

These 12 tools become available when you connect Findymail to CrewAI via MCP:

create_contact_list

Create a new contact list

enrich_company

Enrich company data

find_email

Find a verified email address

find_phone

Find direct phone numbers

get_contact

Get contact details

get_credits

Check credit balance

get_credits_summary

Get credits usage summary

get_lead_search_data

Get lead search results

get_lead_search_status

Check lead search status

list_contact_lists

List all contact lists

search_leads

Find companies and contacts

verify_email

Verify an email address

Example Prompts for Findymail in CrewAI

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

"Find the verified email for Satya Nadella at microsoft.com"

"Enrich company data for the domain 'vinkius.com'"

"Search for 'marketing agency owners in New York' using Intellimatch."

Troubleshooting Findymail MCP Server with CrewAI

Common issues when connecting Findymail 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.

Findymail + CrewAI FAQ

Common questions about integrating Findymail 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.