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.
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.
- 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.
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.
One command plus a key — pip install leadenrich-mcp, then supply credentials