com.mambabuilt/mcp-email-waterfall-orchestrator
NPM · @MAMBALABSDEV/MCP-EMAIL-WATERFALL-ORCHESTRATOR · SCANNED OCT 1
Finds and verifies work emails on your own provider keys, with real per-provider spend.
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 → Why this is hard to 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
- 31 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 48 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 591 tokens (~591/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 Management93
- Stability observed for 28 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
How do I install the com.mambabuilt/mcp-email-waterfall-orchestrator server?
com.mambabuilt/mcp-email-waterfall-orchestrator runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-email-waterfall-orchestrator. 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-email-waterfall-orchestrator
claude mcp add com-mambabuilt-mcp-email-waterfall-orchestrator -- npx -y @mambalabsdev/mcp-email-waterfall-orchestrator
{
"mcpServers": {
"com-mambabuilt-mcp-email-waterfall-orchestrator": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-email-waterfall-orchestrator"
]
}
}
} {
"servers": {
"com-mambabuilt-mcp-email-waterfall-orchestrator": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-email-waterfall-orchestrator"
]
}
}
} codex mcp add com-mambabuilt-mcp-email-waterfall-orchestrator -- npx -y @mambalabsdev/mcp-email-waterfall-orchestrator
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mambabuilt-mcp-email-waterfall-orchestrator": {
"type": "local",
"command": [
"npx",
"-y",
"@mambalabsdev/mcp-email-waterfall-orchestrator"
],
"enabled": true
}
}
} openclaw mcp add com-mambabuilt-mcp-email-waterfall-orchestrator --command npx --arg -y --arg @mambalabsdev/mcp-email-waterfall-orchestrator
mcp_servers:
com-mambabuilt-mcp-email-waterfall-orchestrator:
command: "npx"
args: ["-y", "@mambalabsdev/mcp-email-waterfall-orchestrator"] {
"McpServers": {
"com-mambabuilt-mcp-email-waterfall-orchestrator": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mambalabsdev/mcp-email-waterfall-orchestrator"
]
}
}
} assistant mcp add com-mambabuilt-mcp-email-waterfall-orchestrator -t stdio -c npx -a -y @mambalabsdev/mcp-email-waterfall-orchestrator
{
"mcpServers": {
"com-mambabuilt-mcp-email-waterfall-orchestrator": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-email-waterfall-orchestrator"
]
}
}
} 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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −3
- Stability: pass → 0.80 functional
- 26 Sept 26 0
- Stability: 0.97 → pass security
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
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 1 Oct 2026 · Analysed npm/@mambalabsdev/mcp-email-waterfall-orchestrator@1.0.2
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 →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
find_work_email Find Work Email ~591
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.
| Name | Type | Req | Description |
|---|---|---|---|
| concurrencyHint | integer | – | Advisory only. Real pacing comes from each endpoint's own documented rate limits, which are multi-window and per endpoint, so this cannot exceed them. |
| contacts | array | – | One object per person. Each may carry full_name, first_name, last_name, company_domain, company_name, linkedin_url and email. A single contact is an array of one. Omit it or pass an empty array and t… |
| maxContacts | integer | – | Hard ceiling on how many contacts are processed. Leave empty for no ceiling. |
| maxProviderUnits | integer | – | Run-level cap on the provider credits this run may consume from YOUR accounts. When it is reached the remaining contacts are skipped with a reason rather than spent on. Strongly recommended. |
| providerKeys | object | – | YOUR own provider API keys, keyed by provider name. Validated for free before any paid call. A provider with no usable key is dropped and reported rather than failing the run. |
| providerOrder | array | – | Registry entry ids in the order you want them called. Leave empty for the actor's default order. |
| providerRates | object | – | Optional map of provider or provider.endpoint to YOUR cost per unit, for example {"findymail.search_name": 0.0198}. Supply it and the run reports dollars at your rate; leave it empty and it reports u… |
| verificationOrder | array | – | Verifier entry ids in order. Leave empty for the actor's default order. |
No output schema declared.
No examples provided.
What is the com.mambabuilt/mcp-email-waterfall-orchestrator server?
com.mambabuilt/mcp-email-waterfall-orchestrator is listed in the public MCP registry as com.mambabuilt/mcp-email-waterfall-orchestrator. Finds and verifies work emails on your own provider keys, with real per-provider spend. This page covers its npm package (@mambalabsdev/mcp-email-waterfall-orchestrator).
Is the com.mambabuilt/mcp-email-waterfall-orchestrator server safe to use?
com.mambabuilt/mcp-email-waterfall-orchestrator scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 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-email-waterfall-orchestrator server expose?
com.mambabuilt/mcp-email-waterfall-orchestrator exposes 1 tool: find_work_email. Their descriptions and schemas cost roughly 591 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-email-waterfall-orchestrator server still maintained?
com.mambabuilt/mcp-email-waterfall-orchestrator is still listed as active in the MCP registry. We last reached this channel on 1 October 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-email-waterfall-orchestrator server under?
com.mambabuilt/mcp-email-waterfall-orchestrator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.