io.github.carsonroell-debug/leadenrich-mcp
PYPI · LEADENRICH-MCP
Waterfall lead enrichment — cascades Apollo, Clearbit, and Hunter for max coverage
Available components
Last scanned (13 hours ago)
Scores higher than 82% of PyPI servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 212 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 576 tokens (~82/item across 7 items; 6 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/leadenrich-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_usage Check Usage ~35
Check your current usage and remaining quota.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | Your LeadEnrich API key. Uses server default if not provided. |
Structured output declared, but exposes no named fields.
No examples provided.
enrich_batch Enrich Batch ~76
Enrich multiple leads concurrently. Each lead cascades through all providers.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | Your LeadEnrich API key for usage tracking. |
| leads | array | yes | List of lead objects, each with optional keys: email, domain, first_name, last_name. |
| providers | – | – | Optional list to limit which providers to use. |
Structured output declared, but exposes no named fields.
No examples provided.
enrich_company Enrich Company ~71
Enrich a company by domain. Returns firmographic data without person-level details. Best for account-level research: industry, size, revenue, description, etc.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | Your LeadEnrich API key for usage tracking. |
| domain | string | yes | Company domain (e.g. "stripe.com"). |
Structured output declared, but exposes no named fields.
No examples provided.
enrich_lead Enrich Lead ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | Your LeadEnrich API key for usage tracking. |
| domain | – | – | Company domain (e.g. "stripe.com"). |
| – | – | Contact email address (best identifier). | |
| first_name | – | – | Contact's first name (combine with last_name + domain). |
| last_name | – | – | Contact's last name. |
| providers | – | – | Optional list to limit which providers to use. Default: all configured. |
Structured output declared, but exposes no named fields.
No examples provided.
find_email Find Email ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | Your LeadEnrich API key for usage tracking. |
| domain | string | yes | Company domain (e.g. "stripe.com"). |
| first_name | string | yes | Contact's first name. |
| last_name | string | yes | Contact's last name. |
Structured output declared, but exposes no named fields.
No examples provided.
health_check Health Check ~32
Check server health and which enrichment providers are configured. Returns server status, configured providers, cache stats, and connectivity info.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.carsonroell-debug/leadenrich-mcp server?
io.github.carsonroell-debug/leadenrich-mcp runs locally as a PyPI package, launched with uvx leadenrich-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · leadenrich-mcp
claude mcp add carsonroell-debug-leadenrich-mcp -- uvx leadenrich-mcp
What is the io.github.carsonroell-debug/leadenrich-mcp server?
io.github.carsonroell-debug/leadenrich-mcp is listed in the public MCP registry as io.github.carsonroell-debug/leadenrich-mcp. Waterfall lead enrichment, cascades Apollo, Clearbit, and Hunter for max coverage. This page covers its PyPI package (leadenrich-mcp).
Is the io.github.carsonroell-debug/leadenrich-mcp server safe to use?
io.github.carsonroell-debug/leadenrich-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.carsonroell-debug/leadenrich-mcp server expose?
io.github.carsonroell-debug/leadenrich-mcp exposes 6 tools: enrich_lead, find_email, enrich_company, enrich_batch, check_usage, health_check. Their descriptions and schemas cost roughly 478 tokens of context every time the server is loaded.
Is the io.github.carsonroell-debug/leadenrich-mcp server still maintained?
io.github.carsonroell-debug/leadenrich-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.carsonroell-debug/leadenrich-mcp server under?
io.github.carsonroell-debug/leadenrich-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.