Mobile Phone Waterfall Orchestrator MCP server

Mobile Phone Waterfall MCP Server

Find a mobile phone number for each contact by calling your own phone data providers in order, Prospeo, Lusha, ContactOut, and FullEnrich, until one returns a number. One row per contact with the number in E.164 format, line type, country, a Do Not Call flag where the provider reports one, and the provider credits it spent.

It runs the Mobile Phone Waterfall actor (Actor ID 6OOgPktf7RIa5XCOP) on Apify.

The Prospeo path has been run live on a real key (2026-10-19). The Lusha, ContactOut, and FullEnrich steps are built to each provider's documented API but have not yet been run on a live key; every run summary lists them under providersnotlive_verified. No key is stored.

Tool

Setup

{
  "mcpServers": {
    "mamba-mobile-phone-waterfall-orchestrator": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-mobile-phone-waterfall-orchestrator"],
      "env": {
        "APIFY_TOKEN": "your-apify-token",
        "PROSPEO_API_KEY": "optional",
        "LUSHA_API_KEY": "optional",
        "CONTACTOUT_API_KEY": "optional",
        "FULLENRICH_API_KEY": "optional"
      }
    }
  }
}

APIFY_TOKEN is required to run the tool. The provider keys are optional and read from this server's environment, so they never pass through the model's context. With no provider key set, the run completes, calls nothing, and charges only the run start fee.

Inputs

contacts (each with any of fullname, firstname, lastname, companydomain, companyname, linkedinurl, email, id), or the single contact shortcuts fullname, companydomain, linkedinurl, email. Optional: providerorder, mobileonly, maxcontacts, maxprovidercredits, maxchargeusd.

A LinkedIn URL is passed to providers as an identifier. Neither this server nor the actor opens it.

How it runs

Shortened. The full README is on GitHub.