Mcp Email Waterfall Orchestrator

com.mambabuiltPublished by mambabuilt.comv1.2.1Updated Nov 7, 2026

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

VerifiedSTDIODesktop onlyWeb Search & ScrapingCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Local MCP server that finds and verifies work emails for contacts using your own finder provider keys, with per-provider spend attribution.

What you can do
  • Find work emails for a list of contacts by running a chain of finder providers on your own provider API keys
  • Verify each address as soon as a finder returns it, so undeliverable hits are flagged before use
  • Report one row per contact, misses included, plus a summary row with the provider that found the address, its chain position, providers attempted, verification verdict and units spent
  • Cap spend with a run-level provider unit limit and an optional USD charge cap, and report dollars when you supply your own provider rates
When to use it
Useful when you already hold accounts and negotiated rates with email finder providers and want an assistant to run enrichment and verification over a contact list while keeping spend visible per provider. It suits go-to-market or sales data work where you want to compare which provider actually delivers hits.
Requirements
Runs locally over stdio via npx, so Node.js is needed. Requires an Apify account and an APIFY_TOKEN environment variable, plus your own API keys for each finder and verifier provider passed in the tool call. Network access to Apify and the providers is required.
Before you install
Calls spend real money: Apify credits are charged per contact submitted and per address found, and each run also spends from your own provider accounts. Set maxProviderUnits and max_charge_usd to bound costs. Provider keys are supplied in the tool call, so treat them as secrets. Contact data, including names, domains and LinkedIn URLs, is sent to Apify and third-party providers.

Installation

In SourceWeft

  1. Open Mcp Email Waterfall Orchestrator 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

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.

Source: README.md at commit 7bea7b7

Tools

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.

ParameterscontactsmaxContactsproviderKeysproviderOrderproviderRatesmax_charge_usdconcurrencyHintmaxProviderUnitsverificationOrder

Version history

5
  1. v1.2.1LatestNov 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

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