Leadenrich Mcp

io.github.carsonroell-debugPublished by GitHub account carsonroell-debugv0.2.0Updated Oct 24, 2026

Waterfall lead enrichment — cascades Apollo, Clearbit, and Hunter for max coverage

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

A local MCP server that enriches leads and companies by cascading Apollo, Clearbit and Hunter into one merged profile with per-field attribution.

What you can do
Enrich a single lead from an email, domain, or name plus domain, with a merged profile, confidence score and lookup cost, and optionally limit which providers run. Find a contact's email from first name, last name and company domain, with verification status. Pull company firmographics such as industry, size, revenue, description and location from a domain. Batch-enrich up to 25 leads at once and get a batch summary. Check usage, cost, tier and remaining quota, and inspect server status, configured providers and cache statistics.
When to use it
Useful when an assistant needs to build or complete sales and marketing lead profiles, look up company details from a domain, or find and verify contact emails, especially when you already pay for one or more of the Apollo, Clearbit or Hunter APIs and want their results merged in one call.
Requirements
Runs locally as a Python package (Python 3.11+ and pip); the README also describes an HTTP endpoint on localhost port 8300. Provider keys APOLLO_API_KEY, CLEARBIT_API_KEY and HUNTER_API_KEY are optional, and the server uses whichever are configured. Network access to the provider APIs is needed. A LEADENRICH_API_KEY and a paid Pro tier are mentioned for full features.
Before you install
Lookups cost money: the README lists $0.05 to $0.15 per lookup depending on how many providers return data, plus a $29/month Pro tier for the full waterfall, email finder, company enrichment and batch tools. The free tier is limited to 50 lookups per month and Hunter-only enrichment. Sending personal data such as names, emails and domains to Apollo, Clearbit and Hunter shares it with third parties. Provider keys are secrets and should be kept out of shared configuration.

Installation

In SourceWeft

  1. Open Leadenrich Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

LeadEnrich MCP Server

[License: MIT] [Python 3.11+] [PyPI] [MCP] [MCPize]

Waterfall lead enrichment for AI agents. Cascades through Apollo, Clearbit, and Hunter to build the most complete lead profile in a single call.

One-click install: Install on MCPize | pip install leadenrich-mcp

LeadEnrich MCP exposes lead and company enrichment through the Model Context Protocol (MCP), so tools like Claude and Cursor can run enrichment workflows directly. Give it an email, domain, or name and it returns a merged profile with field attribution showing which provider contributed each data point.

Quick Connect

1. Install and start the server

bash
pip install leadenrich-mcpleadenrich-mcp

The server starts on http://localhost:8300/mcp by default.

2a. Connect from Claude Desktop

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "leadenrich": {      "url": "http://localhost:8300/mcp"    }  }}

2b. Connect from Claude Code

bash
claude mcp add leadenrich --transport http http://localhost:8300/mcp

Tools

ToolDescription
enrich_leadFull waterfall enrichment for a single lead (email, domain, or name+domain)
find_emailDiscover an email from first name + last name + company domain
enrich_companyCompany firmographic data by domain (industry, size, revenue, etc.)
enrich_batchBatch enrich up to 25 leads concurrently
check_usageQuota, cost tracking, and remaining lookups
health_checkServer status, configured providers, and cache stats

How It Works

LeadEnrich uses a waterfall strategy: each provider fills gaps left by the previous one. When email is known, all providers run concurrently for speed. When only name+domain is provided, Apollo discovers the email first, then Clearbit and Hunter run in parallel.

Input (email / domain / name+domain)         |         v  +-----------+     +-----------+     +----------+  |   Apollo  | --> |  Clearbit | --> |  Hunter  |  +-----------+     +-----------+     +----------+  |  Contact  |     |  Company  |     |  Email   |  |  Company  |     |  Person   |     |  Verify  |  |  LinkedIn |     |  Firmo    |     |  Domain  |  +-----------+     +-----------+     +----------+         |               |                |         v               v                v  +------------------------------------------+  |        Merged Profile                    |  |  16+ fields with per-field attribution   |  |  Confidence score + lookup cost          |  +------------------------------------------+

Each field in the result includes attribution so you know exactly which provider it came from. No duplicate API calls thanks to built-in caching.

Pricing

TierCostDetails
Free$0.0050 lookups/month
1 provider hit$0.05/lookupSingle provider returned data
2 providers hit$0.10/lookupTwo providers contributed fields
3 providers hit$0.15/lookupFull waterfall, maximum coverage

Requirements

  • Python 3.11+
  • pip

Quick Start

bash
git clone https://github.com/carsonlabs/leadenrich-mcp.gitcd leadenrich-mcppip install -r requirements.txtpython main.py

MCP endpoint:

  • http://localhost:8300/mcp

Environment Variables

VariableDescriptionRequired
APOLLO_API_KEYApollo.io API keyNo
CLEARBIT_API_KEYClearbit API keyNo
HUNTER_API_KEYHunter.io API keyNo
LEADENRICH_API_KEYClient auth key for usage meteringNo
LEADENRICH_FREE_TIER_LIMITFree tier limit (default: 50)No
PORTServer port (default: 8300)No

All provider keys are optional. The server uses whichever providers are configured and skips the rest.

Example:

bash
export APOLLO_API_KEY="your-apollo-key"export CLEARBIT_API_KEY="your-clearbit-key"export HUNTER_API_KEY="your-hunter-key"python main.py

Running Options

Run directly:

bash
python main.py

Run via FastMCP CLI:

bash
fastmcp run main.py --transport streamable-http --port 8300

Tool Details

enrich_lead

Inputs:

  • email (optional): Contact email address (best identifier)
  • domain (optional): Company domain (e.g. "stripe.com")
  • first_name / last_name (optional): Contact name (combine with domain)
  • providers (optional): Limit which providers to use
  • api_key (optional): Your LeadEnrich API key

Returns merged lead profile with field attribution, confidence score, and lookup cost.

find_email

Inputs:

  • first_name (required): Contact's first name
  • last_name (required): Contact's last name
  • domain (required): Company domain

Returns discovered email with confidence score and verification status.

enrich_company

Input:

  • domain (required): Company domain

Returns company-level firmographic data: industry, size, revenue, description, location.

enrich_batch

Inputs:

  • leads (required): List of lead objects (max 25), each with optional email/domain/name
  • providers (optional): Limit which providers to use
  • api_key (optional): Your LeadEnrich API key

Returns list of enriched profiles with batch summary.

check_usage

Input:

  • api_key (optional): Your LeadEnrich API key

Returns usage stats: lookup count, cost, tier, remaining quota, and cache stats.

health_check

No input. Returns server status, configured providers, cache stats, and version info.

Try It

bash
fastmcp list-tools main.pyfastmcp call-tool main.py health_check '{}'fastmcp call-tool main.py enrich_lead '{"email":"[email protected]"}'fastmcp call-tool main.py find_email '{"first_name":"Jane","last_name":"Smith","domain":"stripe.com"}'fastmcp call-tool main.py enrich_company '{"domain":"stripe.com"}'

Deployment

Smithery

This repo includes smithery.yaml for Smithery deployment.

  1. Push repository to GitHub
  2. Create/add server in Smithery
  3. Point Smithery to this repository

Docker / Hosting Platforms

A Dockerfile is included for Railway, Fly.io, and other container hosts.

bash
# Railwayrailway up
# Fly.iofly launchfly deploy

Set your provider API keys in your host environment.

Architecture

text
Agent (Claude, Cursor, etc.)  -> MCPLeadEnrich MCP Server (this repo)  -> Apollo API    (contact + company data)  -> Clearbit API  (person + firmographic data)  -> Hunter API    (email finding + verification)

This server is a translation layer between MCP tool calls and multiple enrichment provider APIs, with built-in caching, usage metering, and waterfall merge logic.

Free vs Pro

ToolFreePro ($29/mo)
enrich_leadYes (Hunter only)Yes (full waterfall: Apollo + Clearbit + Hunter)
check_usageYesYes
health_checkYesYes
find_email-Yes
enrich_company-Yes
enrich_batch-Yes

Free tier gives you single-provider lookups via Hunter. Pro unlocks the full 3-provider waterfall, email finder, company enrichment, and batch operations.

Upgrade to Pro on MCPize — $29/mo or $290/yr.


Built by Freedom Engineers

Related

Source: README.md at commit 8c278d1

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.