Bring Lead Enrichment
to LangChain
Learn how to connect CUFinder to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with CUFinder through native MCP adapters. Connect 13 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 CUFinder 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 CUFinder queries for multi-turn workflows
CUFinder in LangChain
CUFinder and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect CUFinder 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 CUFinder in LangChain
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 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
CUFinder for LangChain
Every tool call from LangChain 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 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