com.mambabuilt/mcp-clay-to-instantly-smartlead-push
NPM · @MAMBALABSDEV/MCP-CLAY-TO-INSTANTLY-SMARTLEAD-PUSH · SCANNED AUG 16
Push enriched leads into an Instantly or Smartlead campaign, with ICP gating and dedupe.
Available components
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 →
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 96 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 660 tokens (~660/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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @mambalabsdev/mcp-clay-to-instantly-smartlead-push
claude mcp add com-mambabuilt-mcp-clay-to-instantly-smartlead-p -- npx -y @mambalabsdev/mcp-clay-to-instantly-smartlead-push
codex mcp add com-mambabuilt-mcp-clay-to-instantly-smartlead-p -- npx -y @mambalabsdev/mcp-clay-to-instantly-smartlead-push
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mambabuilt-mcp-clay-to-instantly-smartlead-p": {
"type": "local",
"command": [
"npx",
"-y",
"@mambalabsdev/mcp-clay-to-instantly-smartlead-push"
],
"enabled": true
}
}
} openclaw mcp add com-mambabuilt-mcp-clay-to-instantly-smartlead-p --command npx --arg -y --arg @mambalabsdev/mcp-clay-to-instantly-smartlead-push
mcp_servers:
com-mambabuilt-mcp-clay-to-instantly-smartlead-p:
command: "npx"
args: ["-y", "@mambalabsdev/mcp-clay-to-instantly-smartlead-push"] {
"mcpServers": {
"com-mambabuilt-mcp-clay-to-instantly-smartlead-p": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-clay-to-instantly-smartlead-push"
]
}
}
} 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.
- 16 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Aug 26 +2
- Stability: unverified → 0.13 ▲ functional
- Package version: 1.0.0 → 1.0.1 functional
- 11 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 65
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 16 Aug 2026 · Analysed npm/@mambalabsdev/mcp-clay-to-instantly-smartlead-push@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
push_leads_to_sequencer Push Leads to Sequencer ~660
Push enriched lead rows into an existing Instantly or Smartlead 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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your Instantly v2 API key or your Smartlead 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 dry run with deduplicat… |
| campaign_id | string | yes | The target campaign in the sequencer. It must already exist. Instantly campaign IDs are UUIDs; Smartlead campaign IDs are numeric. |
| custom_variables | array | – | Extra column names to pass through as custom variables under their own name. Columns that are neither mapped nor listed here are dropped. |
| dataset_id | string | – | An Apify dataset ID from an upstream run, for example the output of the ICP Fit Scorer. Used only when leads is empty. |
| deduplicate | boolean | – | 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_run | boolean | – | 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_mapping | object | – | 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… |
| leads | array | – | Lead rows to push. Each row needs an email at minimum. Takes precedence over dataset_id when both are set. |
| min_icp_score | integer | – | Drop leads whose icp_score is below this number. Default 0, which pushes everything. Rows with no icp_score are always kept. |
| sequencer | string | yes | Which sequencer to push to. Instantly uses API v2, Smartlead uses API v1. |
No output schema declared.
No examples provided.