com.mambabuilt/mcp-lead-file-import-checker
NPM · @MAMBALABSDEV/MCP-LEAD-FILE-IMPORT-CHECKER
Check a lead file before import: duplicates, bad emails, MX, websites, and one verdict per row
Available components
Last scanned (9 hours ago)
Scores higher than 38% of npm 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 438 tokens (~438/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 69
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@mambalabsdev/mcp-lead-file-import-checker@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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_lead_file Check a lead file before import ~438
Check a lead list before a CRM or sequencer import. Give one source: rows (a JSON array of objects), csv_url (a public CSV link), or dataset_id (an Apify dataset). Every row comes back with an import_verdict (import, review, or reject), the issues found (invalid email syntax, duplicate, free mail, role address, disposable address, email domain not found or with no MX, parked or unreachable website, company name mismatch, missing required field, stale), and the checks behind them, plus the original row. No mailbox is contacted, so a mailbox can still bounce. Input with nothing to check returns one free row saying why. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per row checked.
| Name | Type | Req | Description |
|---|---|---|---|
| check_websites | string | – | true (default) reads each company homepage once for the live, parked, and company name checks. |
| checks | array | – | Which checks to run. Default all. |
| column_map | object | – | Which of your columns holds email, domain, company, first_name, last_name, and date, for example {"email": "Work Email"}. Without it common header names are read. |
| csv_url | string | – | A public link to a CSV file with a header row, up to 50 MB. |
| dataset_id | string | – | An Apify dataset ID from one of your runs. |
| max_charge_usd | string | – | Optional. The run stops before a charge would pass this amount. |
| max_rows | string | – | Check at most this many rows. Default 5000, at most 50000. |
| required_fields | array | – | Fields a row must have, or it is rejected. Default email. |
| rows | array | – | Lead rows as objects with any column names, up to 50,000. Give rows, csv_url, or dataset_id, one of them. |
| stale_days | string | – | With a date column in column_map, rows older than this many days get the stale issue. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-lead-file-import-checker server?
com.mambabuilt/mcp-lead-file-import-checker runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-lead-file-import-checker. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-lead-file-import-checker
claude mcp add com-mambabuilt-mcp-lead-file-import-checker -- npx -y @mambalabsdev/mcp-lead-file-import-checker
What is the com.mambabuilt/mcp-lead-file-import-checker server?
com.mambabuilt/mcp-lead-file-import-checker is listed in the public MCP registry as com.mambabuilt/mcp-lead-file-import-checker. Check a lead file before import: duplicates, bad emails, MX, websites, and one verdict per row. This page covers its npm package (@mambalabsdev/mcp-lead-file-import-checker).
Is the com.mambabuilt/mcp-lead-file-import-checker server safe to use?
com.mambabuilt/mcp-lead-file-import-checker scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 com.mambabuilt/mcp-lead-file-import-checker server expose?
com.mambabuilt/mcp-lead-file-import-checker exposes 1 tool: check_lead_file. Their descriptions and schemas cost roughly 438 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-lead-file-import-checker server still maintained?
com.mambabuilt/mcp-lead-file-import-checker is still listed as active in the MCP registry. We last reached this channel on 5 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 com.mambabuilt/mcp-lead-file-import-checker server under?
com.mambabuilt/mcp-lead-file-import-checker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.