check_usage
Check your current usage and remaining quota.
LABSCO SUMMARY
The cascade order changes with what you already have, and that is the design rather than an implementation detail.
With an email in hand Apollo, Clearbit and Hunter run concurrently for speed; with only a domain or a name, Apollo runs first because the email has to exist before the others can do anything with it. find_email inverts that preference for its narrower job, going to Hunter's email finder before falling back to Apollo. check_usage and health_check keep the whole thing honest: check_usage reports remaining quota before a batch spends it, and health_check names which providers are actually configured rather than assumed.
What it is
A lead enrichment client with 6 tools that cascade across Apollo, Clearbit and Hunter: single and batch lead enrichment, email finding, company enrichment, a usage check and a health check.
What you get
- enrich_lead takes an email, a domain, or a first and last name with a domain; when an email is supplied all providers run concurrently, and when only a domain or name is given Apollo runs first to discover the email before Clearbit and Hunter run together.
- find_email finds an address from a name and a company domain, using Hunter's purpose-built email finder first and falling back to Apollo people-match.
- enrich_company returns firmographic data for a domain — industry, size, revenue and description — without person-level detail.
- enrich_batch enriches multiple leads concurrently, each cascading through the providers.
- check_usage returns current usage and remaining quota.
- health_check reports server status, which enrichment providers are configured, cache statistics and connectivity.
Requirements
Provider access for whichever of Apollo, Clearbit and Hunter you intend to use — health_check reports which are configured, and an api_key can also travel with an individual call.
Setup effort
One command — pip install leadenrich-mcp
USE CASES
01
Turning a name and a company into a reachable contact
The email finder goes to the provider built for that job first and falls back to a people match, which is a different order from the general cascade.
02
Filling in what you know about a lead you only have an email for
With the email in hand all three providers run at once, so the round trip is one call rather than a chain.
03
Enriching a whole list at once
Batch runs the same cascade per lead concurrently, and checking the quota first is what stops it stopping halfway.
04
Researching an account without person-level data
Company enrichment stops at firmographics by design, which is the right call when the question is about the account rather than a contact.
05
Finding out why enrichment is coming back empty
The health read names which providers are actually configured, which is the first thing to check before blaming the data.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
enrich_batch
Enrich multiple leads concurrently. Each lead cascades through all providers.
enrich_company
Enrich a company by domain. Returns firmographic data without person-level details.
Best for account-level research: industry, size, revenue, description, etc.
enrich_lead
Enrich a single lead by cascading through Apollo, Clearbit, and Hunter.
Provide at least one of: email, domain, or first_name + last_name + domain. When email is provided, all providers run concurrently for speed. When only domain/name is provided, Apollo runs first to discover the email, then Clearbit + Hunter run concurrently.
find_email
Find someone's email address given their name and company domain.
Uses Hunter email-finder first (purpose-built for this), then falls back to Apollo people-match if Hunter doesn't find it.
health_check
Check server health and which enrichment providers are configured.
Returns server status, configured providers, cache stats, and connectivity info.
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected. find_email, enrich_company and enrich_batch require Pro ($29/mo); the free tier gives enrich_lead through Hunter plus check_usage and health_check.
Requires
Python 3.11+
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install leadenrich-mcpMCP Clients
Claude Desktop
pip install leadenrich-mcp puts the leadenrich-mcp command on your PATH. Keep only the provider keys you have and delete the rest; health_check reports which providers are configured.
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"leadenrich": {
"command": "leadenrich-mcp",
"env": {
"APOLLO_API_KEY": "<YOUR_APOLLO_API_KEY>",
"CLEARBIT_API_KEY": "<YOUR_CLEARBIT_API_KEY>",
"HUNTER_API_KEY": "<YOUR_HUNTER_API_KEY>"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add leadenrich -e APOLLO_API_KEY=<YOUR_APOLLO_API_KEY> -e CLEARBIT_API_KEY=<YOUR_CLEARBIT_API_KEY> -e HUNTER_API_KEY=<YOUR_HUNTER_API_KEY> -- leadenrich-mcp
