Mcp Lead File Import Checker

com.mambabuiltPublished by mambabuilt.comv1.0.0Updated Nov 3, 2026

Check a lead file before import: duplicates, bad emails, MX, websites, and one verdict per row

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Checks a lead list before CRM or sequencer import, returning an import, review, or reject verdict per row with the issues behind it.

What you can do
  • Check lead rows for import readiness, from a JSON row array, a public CSV link, or an Apify dataset
  • Flag email syntax problems, duplicates as inboxes see them, free mail, role inboxes, disposable domains, and DNS/MX records
  • Read each company homepage once to spot parked or dead sites and company name mismatches
  • Report missing required fields and stale dates, with configurable checks, column mapping, row limits, and an optional cost cap
When to use it
Use it when you are about to load a lead file into a CRM or outreach sequencer and want to separate clean rows from ones needing review or rejection. It suits list hygiene questions such as counting duplicates and role addresses or finding companies with dead websites.
Requirements
Runs locally as an npm package via npx, so Node.js 18 or newer is needed. An Apify account and an Apify API token set as APIFY_TOKEN are required for calls; the tool is listed without one. Network access is needed because the work runs on Apify.
Before you install
Calls spend money: the run is billed per row checked plus a per-run start fee to your Apify account, so set max_charge_usd if cost matters. Lead data you submit, including CSV links and Apify dataset IDs, is sent to Apify for processing, and company homepages are fetched. The APIFY_TOKEN is a secret and should be kept out of shared configs. It does not verify mailboxes.

Installation

In SourceWeft

  1. Open Mcp Lead File Import Checker 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

Lead File Import Checker MCP Server

[npm version] [license]

An MCP server for the Mamba Labs Lead File Import Checker actor on Apify. Give it lead rows, a CSV link, or an Apify dataset. Every row comes back with an import, review, or reject verdict and the issues behind it, so only clean rows reach your CRM or sequencer.

What's Inside

What it does

Checks per row: email syntax, duplicates (the way inboxes see them, so [email protected] matches [email protected]), free mail, role inboxes, disposable domains, DNS and MX for the email domain, one homepage read per company domain for live, parked, and company name checks, missing required fields, and stale dates. It does not verify mailboxes and never contacts a mail server. All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

json
{  "mcpServers": {    "mamba-lead-file-import-checker": {      "command": "npx",      "args": [        "-y",        "@mambalabsdev/mcp-lead-file-import-checker"      ],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Restart the client. The check_lead_file tool appears.

Prerequisites

Example prompts

  • "Check this lead CSV and give me only the rows marked import."
  • "How many duplicates and role addresses are in this list?"
  • "Which of these companies have a parked or dead website?"

Tool

check_lead_file. One tool. Example arguments:

json
{  "rows": [    { "Email": "[email protected]", "Company": "Stripe" },    { "Email": "[email protected]", "Company": "Gong" }  ]}

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults. Numbers and yes or no options are sent as strings.

InputTypeDescription
rowsarrayLead rows as objects, up to 50,000
csv_urlstringA public CSV link, up to 50 MB
dataset_idstringAn Apify dataset ID
column_mapobjectWhich column holds each field
required_fieldsarrayFields a row must have. Default email
checksarrayWhich checks to run. Default all
check_websitesstringtrue (default) or false
stale_daysstringDays before a dated row is stale
max_rowsstringDefault 5000, at most 50000
max_charge_usdstringOptional cost cap for the run

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
row-checked, per row of your file checked$0.002$0.0019$0.0018$0.0017
apify-actor-start, per run start$0.001$0.001$0.001$0.001

Blank rows, rows over max_rows, and the one row a refused input writes are free.

Your keys

The actor needs no key and holds none. It reads DNS and the companies' own homepages. Mamba Labs pays the platform costs of the run.

Full actor documentation

apify.com/mambalabs/lead-file-import-checker

License

MIT. See LICENSE.

Source: README.md at commit 7b2d483

Tools

1

check_lead_file

Check a lead file before import

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.

Parametersrowscheckscsv_urlmax_rowscolumn_mapdataset_idstale_dayscheck_websitesmax_charge_usdrequired_fields

Version history

1
  1. v1.0.0LatestNov 1, 2026

Score

90% 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
  • 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts