# com.mambabuilt/mcp-email-waterfall-orchestrator (npm · @mambalabsdev/mcp-email-waterfall-orchestrator)

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

- Trust score: 71/100 (medium)
- Change this week: +9
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-17

## Components

- npm · `@mambalabsdev/mcp-email-waterfall-orchestrator`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-mambabuilt-mcp-email-waterfall-orchestrator/mambalabsdev-mcp-email-waterfall-orchestrator.md), [page](https://verifymcp.io/servers/com-mambabuilt-mcp-email-waterfall-orchestrator/mambalabsdev-mcp-email-waterfall-orchestrator)

## Channel facts

- Registry: `npm`
- Package: `@mambalabsdev/mcp-email-waterfall-orchestrator`
- Version: `1.0.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-17.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add com-mambabuilt-mcp-email-waterfall-orchestrator -- npx -y @mambalabsdev/mcp-email-waterfall-orchestrator
```

### Codex

```bash
codex mcp add com-mambabuilt-mcp-email-waterfall-orchestrator -- npx -y @mambalabsdev/mcp-email-waterfall-orchestrator
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add com-mambabuilt-mcp-email-waterfall-orchestrator --command npx --arg -y --arg @mambalabsdev/mcp-email-waterfall-orchestrator
```

### Hermes

```yaml
mcp_servers:
  com-mambabuilt-mcp-email-waterfall-orchestrator:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-email-waterfall-orchestrator"]
```

### Other

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-email-waterfall-orchestrator": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-email-waterfall-orchestrator"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-16 (score 71, +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.

### 2026-08-14 (score 70, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

### 2026-08-13 (score 59, −7)

- [security regression] Known CVEs: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Dependency health: 0.85 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.0.0 → 1.0.2

### 2026-08-11 (score 66, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-09 (score 62)

First indexed and scored.

## MCP tools (1)

### `find_work_email` (~591 tokens)

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.

Input parameters:

- `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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-mambabuilt-mcp-email-waterfall-orchestrator/mambalabsdev-mcp-email-waterfall-orchestrator#diagnostics

## Score history

- 2026-08-17: 71
- 2026-08-16: 71
- 2026-08-15: 70
- 2026-08-14: 70
- 2026-08-13: 59
- 2026-08-12: 66
- 2026-08-11: 66
- 2026-08-10: 62
- 2026-08-09: 62

## Links

- npm package: https://www.npmjs.com/package/@mambalabsdev/mcp-email-waterfall-orchestrator
- Socket report: https://socket.dev/npm/package/@mambalabsdev/mcp-email-waterfall-orchestrator
- Repository: https://github.com/mambalabsdev/mcp-email-waterfall-orchestrator
- Changelog RSS feed: https://verifymcp.io/servers/com-mambabuilt-mcp-email-waterfall-orchestrator/mambalabsdev-mcp-email-waterfall-orchestrator.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mambabuilt-mcp-email-waterfall-orchestrator/mambalabsdev-mcp-email-waterfall-orchestrator.json
- HTML version of this page: https://verifymcp.io/servers/com-mambabuilt-mcp-email-waterfall-orchestrator/mambalabsdev-mcp-email-waterfall-orchestrator