Bring Contact Discovery
to LangChain
Learn how to connect ContactOut to LangChain and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the ContactOut MCP Server?
Connect your ContactOut account to any AI agent to streamline your B2B lead generation and talent acquisition workflows through natural conversation. ContactOut provides a powerful intelligence layer for discovering verified contact information and enriching professional profiles at scale.
What you can do
- Contact Discovery Orchestration — Instantly retrieve verified email addresses and direct phone numbers using LinkedIn profile URLs programmatically
- Professional Enrichment — Enrich contact and company data with detailed attributes, including job titles, locations, and social links to maintain a high-fidelity CRM
- Deep Semantic Search — Programmatically search the ContactOut database of 300M+ people using advanced filters for skills, titles, and locations
- Identity Resolution — Find the LinkedIn profile associated with a specific email address to perfectly coordinate your multichannel outreach
- Administrative Visibility — Programmatically track your credit balance and API usage statistics to coordinate your recruitment and sales budgets
How it works
1. Subscribe to this server
2. Retrieve your API Key from your ContactOut dashboard (Settings > API)
3. Start finding decision-makers and enriching your lead lists from Claude, Cursor, or any MCP client
No more manual profile scraping or guessing email formats. Your AI acts as your dedicated sales associate and recruitment coordinator.
Who is this for?
- Sales Development (SDRs) — build highly targeted outreach lists with verified contact info using natural language commands
- Technical Recruiters — search for candidates with specific skills and retrieve contact details without leaving your workspace
- Growth Marketers — automate lead enrichment and identify LinkedIn profiles from email lists through simple AI queries
Built-in capabilities (7)
Enrich company data
Enrich contact data
Find email by LinkedIn profile
Find LinkedIn profile by email
Get API usage statistics
Search for companies
Search for people
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with ContactOut through native MCP adapters. Connect 7 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine ContactOut MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across ContactOut queries for multi-turn workflows
ContactOut in LangChain
ContactOut and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ContactOut to LangChain 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 ContactOut in LangChain
The ContactOut 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 7 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain 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
ContactOut for LangChain
Every tool call from LangChain to the ContactOut MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my ContactOut API Key?
Log in to your account, navigate to Settings > API, and copy your unique access token.
Can I search for people by skills and location?
Yes! The search_people tool accepts a JSON object with filters like skills, location, and job_title programmatically.
How do I find an email using a LinkedIn URL?
Use the find_email_by_linkedin tool and provide the full LinkedIn profile URL to retrieve verified contact details.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters