Mcp Email Waterfall Orchestrator

com.mambabuilt由 mambabuilt.com 發布v1.2.1更新於 Nov 7, 2026

Finds and verifies work emails on your own provider keys, with real per-provider spend.

已驗證STDIO僅桌面網頁搜尋與抓取溝通與協作商業與電商

概覽

AI 產生的概覽

本機 MCP 伺服器，使用你自己的查找服務商金鑰為聯絡人尋找並驗證工作信箱，並依服務商提供真實花費歸因。

可以做什麼
  • 用你自己的服務商 API 金鑰，依鏈條順序呼叫多個查找服務商，為一批聯絡人尋找工作信箱
  • 每個服務商回傳地址後立即驗證，提前標出無法投遞的「命中」
  • 依聯絡人逐列回傳結果（含未命中），並附一列彙總：命中的服務商、其在鏈中的位置、嘗試過的服務商、驗證結論與消耗單位數
  • 可用執行層級的服務商單位上限與可選的美元費用上限控制支出；提供自己的費率時以美元回報花費
適用情境
適合已擁有信箱查找服務商帳號與議定價格、希望讓助理對聯絡人名單批次做補齊與驗證，並看清各服務商實際花費的情境。也適合需要比較哪家服務商真正帶來有效命中的業務或行銷資料工作。
執行需求
透過 npx 以 stdio 在本機執行，需要 Node.js。需要 Apify 帳號與 APIFY_TOKEN 環境變數，並在工具呼叫中傳入你自己的各查找與驗證服務商 API 金鑰。需要連線至 Apify 及各服務商的網路。
安裝前請注意
會產生實際費用：Apify 依送出的聯絡人與找到的地址計費，每次執行還會從你自己的服務商帳戶扣款。建議設定 maxProviderUnits 與 max_charge_usd 限制成本。服務商金鑰在工具呼叫中傳入，應視為機密處理。聯絡人資料（姓名、網域、LinkedIn 連結等）會傳送給 Apify 與第三方服務商。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Mcp Email Waterfall Orchestrator，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Work Email Waterfall MCP Server

[npm] [MCP] [License: MIT]

[Email Waterfall Orchestrator MCP server]

MCP server for the Mamba Labs Work Email Waterfall actor on Apify.

Give it contacts and your own provider API keys. It finds a work email for each, verifies it, and tells you exactly what each provider cost you.

Tool

find_work_email

Returns one flat row per contact, misses included, plus a summary row carrying the run totals: the address found, which provider found it, its position in the chain, every provider attempted, the verification verdict and its source, and the provider units spent.

Bring your own keys

This is the part that makes it different from a credit-based enrichment tool. Mamba Labs supplies no provider keys, never sees your credits, and never resells them. The run spends from your accounts at your negotiated rates, which is why maxProviderUnits exists and why you should set it.

The tradeoff is honest in both directions: you keep your own pricing and your own provider relationships, and you carry your own spend. What you get back is real attribution rather than a credit count, so you can see which provider actually earned its keep.

Give it providerRates and the run reports dollars at your rate. Leave it empty and it reports units only, because your plan tier is not knowable from here and guessing it would produce a confident wrong number.

What happens to a bad key

Nothing dramatic. Every key is validated for free before any paid call. A provider with no usable key is dropped from the chain and reported, rather than failing the run or silently burning attempts. With no keys at all the run still completes, explains which capabilities were unavailable, and charges nothing.

Verification is not an afterthought

Verification runs after each finder that returns an address, not once at the end, because providers do not agree on what "found" means. An address that one provider calls a hit and a verifier calls undeliverable is a miss, and you want to know that before it reaches a sequencer.

find_work_email

InputTypeNotes
contactsobject[]One object per person. Any of full_name, first_name, last_name, company_domain, company_name, linkedin_url, email. A single contact is an array of one.
providerKeysobjectYour own keys, by provider name. Validated for free before any paid call.
providerOrderstring[]Registry entry ids in call order. Empty means the actor's default chain.
verificationOrderstring[]Verifier entry ids in order. Empty means the actor's default.
maxContactsintegerHard ceiling on contacts processed.
maxProviderUnitsintegerRun-level cap on provider credits spent from your accounts. Strongly recommended.
providerRatesobjectMap of provider or provider.endpoint to your cost per unit, so spend is reported in dollars.
concurrencyHintintegerAdvisory. Real pacing comes from each endpoint's own multi-window rate limits.
max_charge_usdnumberOptional cost cap in USD for this run. The actor stops before an item that could take its charges past this amount.

More identifiers means a better chance of a hit. Keyed on a LinkedIn URL the top provider measured 13.7 percent against 9.3 percent on name plus domain, on the same 300 contacts in the same hour.

Setup

json
{  "mcpServers": {    "mamba-email-waterfall-orchestrator": {      "command": "npx",      "args": ["-y", "@mambalabsdev/mcp-email-waterfall-orchestrator"],      "env": { "APIFY_TOKEN": "your-apify-token" }    }  }}

Get a token at console.apify.com/account/integrations. Each call spends from your own provider accounts and consumes Apify credits per contact submitted and per address found, on top of whatever your own provider keys spend.

Pricing

Price per event on the Apify FREE plan, from the live pricing record; paid Apify plans pay less per event.

EventPrice (USD)
Actor Start (apify-actor-start)0.00005
Email Search Submitted (email-search-submitted)0.003
Email Found (email-found)0.02

Also available

This tool is also exposed by the GTM Suite umbrella server, alongside the rest of the Mamba Labs GTM actors, if you would rather run one server than many.

Built by Mamba Labs.

來源：README.md，提交 7bea7b7

工具

1

find_work_email

Find Work Email

Find a work email address for each contact by running a chain of finder providers on YOUR OWN provider API keys, verify each result, and return real per-provider spend attribution instead of an opaque credit count. This is bring your own key: Mamba Labs supplies no provider keys, never sees your credits, and the run spends from your accounts, so set maxProviderUnits. Supply contacts as an array of objects, each carrying any of full_name, first_name, last_name, company_domain, company_name, linkedin_url and email. More identifiers means a better chance of a hit. Supply your keys in providerKeys by provider name. Every key is validated for free before any paid call, and a provider with no usable key is dropped from the chain and reported rather than failing the run; with no keys at all the run still completes, explains what was unavailable and charges nothing. Verification runs after each finder that returns an address, not once at the end. Every contact gets a row including misses, so you can see what was attempted, and a final summary row carries the run totals and spend. Returns flat Clay-ready JSON. Requires an APIFY_TOKEN and consumes Apify credits per contact submitted and per address found, on top of whatever your own provider keys spend.

輸入參數contactsmaxContactsproviderKeysproviderOrderproviderRatesmax_charge_usdconcurrencyHintmaxProviderUnitsverificationOrder

版本歷史

5
  1. v1.2.1最新Nov 5, 2026
  2. v1.2.0Oct 16, 2026
  3. v1.1.1Oct 6, 2026
  4. v1.1.0Oct 6, 2026
  5. v1.0.2Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分