Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mambabuilt/mcp-clay-to-instantly-smartlead-push

NPM · @MAMBALABSDEV/MCP-CLAY-TO-INSTANTLY-SMARTLEAD-PUSH

Push enriched leads into an Instantly or Smartlead campaign, with ICP gating and dedupe.

0 this week 77 Trust /100

Last scanned (13 hours ago)

Scores higher than 56% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 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 16 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 778 tokens (~778/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 Management97
  • Stability observed for 29 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 0
    • Stability: pass → 0.97 functional
  • 13 Nov 26 0
    • Stability: 0.97 → pass security
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 6 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
    • Package version: 1.3.0 → 1.3.1 functional
  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
Diagnostics

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 21 Nov 2026 · Analysed npm/@mambalabsdev/mcp-clay-to-instantly-smartlead-push@1.3.1

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~778 tokens

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 →

Tool Tokens
push_leads_to_sequencer ~778

Push enriched lead rows into an existing Instantly, Smartlead, or HeyReach campaign. Maps common Clay column names onto each sequencer's own field names, optionally drops leads below a minimum ICP score, optionally deduplicates against the leads already in the destination campaign, and sends the rest in batches. Returns one flat summary row: how many leads were received, dropped for having no usable email, dropped by the ICP gate, dropped as duplicates, eligible, actually created by the sequencer, skipped by the sequencer, and failed, plus the vendor's own error message per failed address. The campaign must already exist; this does not create campaigns or write sequence copy. Set dry_run true to get back the exact request payload that would be sent without creating a single lead and without being charged, which is the safe way to check a mapping against a new campaign. Billing is per lead the sequencer confirms it created, so gated, duplicate, skipped, failed and dry-run leads are all free. Instantly uses API v2 and needs a v2 key; Smartlead uses API v1. Requires an APIFY_TOKEN and consumes Apify credits. This WRITES to your sequencer campaign unless dry_run is true.

NameTypeReqDescription
api_keystring–Your Instantly v2 API key, your Smartlead API key or your HeyReach API key. An Instantly v1 key will not work: v1 was deprecated on January 19, 2026. Required for any run that calls the sequencer. A…
campaign_idstringyesThe target campaign in the sequencer. It must already exist. Instantly campaign IDs are UUIDs; Smartlead and HeyReach campaign IDs are numeric.
custom_variablesarray–Extra column names to pass through as custom variables under their own name. Columns that are neither mapped nor listed here are dropped.
dataset_idstring–An Apify dataset ID from an upstream run, for example the output of the ICP Fit Scorer. Used only when leads is empty.
deduplicateboolean–Read the campaign's existing leads first and drop any email already there. Default true. This is a read, so it needs an API key even on a dry run.
dry_runboolean–Run every step, return the exact payload that would be sent, and make zero write calls. Creates no leads and charges nothing. Default false.
field_mappingobject–Override the default Clay column to sequencer field map. Keys are your column names, values are the sequencer field names. Set a value to an empty string to drop that column. A target the sequencer d…
leadsarray–Lead rows to push. Each row needs an email at minimum. Takes precedence over dataset_id when both are set.
max_charge_usdnumber–Optional. The run stops before any charge that would take this run past this amount, and saves every row already paid for. Leave empty to rely only on the maximum cost per run set in Apify, which the…
min_icp_scoreinteger–Drop leads whose icp_score is below this number. Default 0, which pushes everything. Rows with no icp_score are always kept.
sequencerstringyesWhich sequencer to push to. Instantly uses API v2, Smartlead uses API v1, HeyReach uses its public API. HeyReach is LinkedIn native: it keys a lead on linkedin_person_url rather than on email, so a H…

No output schema declared.

No examples provided.

Install

How do I install the com.mambabuilt/mcp-clay-to-instantly-smartlead-push server?

com.mambabuilt/mcp-clay-to-instantly-smartlead-push runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-clay-to-instantly-smartlead-push. 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-clay-to-instantly-smartlead-push

# add to Claude Code
claude mcp add com-mambabuilt-mcp-clay-to-instantly-smartlead-p -- npx -y @mambalabsdev/mcp-clay-to-instantly-smartlead-push
Common questions

What is the com.mambabuilt/mcp-clay-to-instantly-smartlead-push server?

com.mambabuilt/mcp-clay-to-instantly-smartlead-push is listed in the public MCP registry as com.mambabuilt/mcp-clay-to-instantly-smartlead-push. Push enriched leads into an Instantly or Smartlead campaign, with ICP gating and dedupe. This page covers its npm package (@mambalabsdev/mcp-clay-to-instantly-smartlead-push).

Is the com.mambabuilt/mcp-clay-to-instantly-smartlead-push server safe to use?

com.mambabuilt/mcp-clay-to-instantly-smartlead-push scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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-clay-to-instantly-smartlead-push server expose?

com.mambabuilt/mcp-clay-to-instantly-smartlead-push exposes 1 tool: push_leads_to_sequencer. Their descriptions and schemas cost roughly 778 tokens of context every time the server is loaded.

Is the com.mambabuilt/mcp-clay-to-instantly-smartlead-push server still maintained?

com.mambabuilt/mcp-clay-to-instantly-smartlead-push is still listed as active in the MCP registry. We last reached this channel on 21 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-clay-to-instantly-smartlead-push server under?

com.mambabuilt/mcp-clay-to-instantly-smartlead-push declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the com.mambabuilt/mcp-clay-to-instantly-smartlead-push server?

VerifyMCP ran 16 checks on com.mambabuilt/mcp-clay-to-instantly-smartlead-push, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.