Mcp Mobile Phone Waterfall Orchestrator

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

Find mobile phone numbers by chaining your own Prospeo, Lusha, ContactOut, and FullEnrich keys.

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Finds mobile phone numbers for a list of contacts by chaining your own Prospeo, Lusha, ContactOut and FullEnrich keys through an Apify actor.

What you can do
  • Look up mobile numbers for one contact or a batch, using names, company domain, LinkedIn URL or email as identifiers
  • Call your own phone data providers in a chosen order until one returns a number
  • Return one row per contact with the number in E.164 format, line type, country, a Do Not Call flag where reported, and provider credits spent
  • Apply limits such as mobile-only results, maximum contacts, maximum provider credits and a maximum charge in USD
When to use it
Useful when you already hold Apify and phone-data provider accounts and want an assistant to enrich contact lists with mobile numbers in one step, without pasting keys into the chat.
Requirements
Runs locally over stdio via npx (Node.js). Requires an APIFY_TOKEN; the provider keys PROSPEO_API_KEY, LUSHA_API_KEY, CONTACTOUT_API_KEY and FULLENRICH_API_KEY are optional and read from the server's environment. Network access to Apify and the providers is needed.
Before you install
Runs cost money: Apify bills a start event, a charge per contact where a provider was called, and a charge per number found, and each provider spends its own credits on your keys. A run with no provider key set still incurs the start fee. Only the Prospeo path has been run on a live key; the Lusha, ContactOut and FullEnrich steps are unverified. Contact identifiers, including LinkedIn URLs, are sent to third-party providers.

Installation

In SourceWeft

  1. Open Mcp Mobile Phone 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

Mobile Phone Waterfall MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Mobile Phone Waterfall Orchestrator 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 providers_not_live_verified. No key is stored.

Tool

ToolWhat it does
find_mobile_phoneLooks up mobile numbers for a list of contacts on your own provider keys

Setup

json
{  "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 full_name, first_name, last_name, company_domain, company_name, linkedin_url, email, id), or the single contact shortcuts full_name, company_domain, linkedin_url, email. Optional: provider_order, mobile_only, max_contacts, max_provider_credits, max_charge_usd.

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

How it runs

The server starts the actor run (POST /v2/acts/{id}/runs), polls it (GET /v2/actor-runs/{runId}) to a terminal status with a run timeout of 1,800 seconds, and returns the dataset. A run that does not succeed comes back as an error with its run ID.

Cost

Apify charges the actor's pay per event prices to your Apify account: a start event, a charge per contact on which at least one provider was called, and a charge per number found. Your providers charge their own credits on your keys. See the actor's pricing tab for current prices.

License

MIT. Built by Mamba Labs.

Source: README.md at commit d25569a

Tools

1

find_mobile_phone

Find mobile phone

Find a mobile phone number for each contact by calling the buyer's own phone data providers in order (Prospeo, Lusha, ContactOut, FullEnrich) until one returns a number. Returns one row per contact with the number in E.164 format, its line type, country, a Do Not Call flag where the provider reports one, the provider that found it, and the provider credits it spent, plus a run summary row. Provider keys are read from the PROSPEO_API_KEY, LUSHA_API_KEY, CONTACTOUT_API_KEY, and FULLENRICH_API_KEY environment variables of this server; with none set, the run completes, calls nothing, and charges only the run start fee. A LinkedIn URL is passed to providers as an identifier and never opened. A run that does not succeed is returned as an error with its run ID. Requires an APIFY_TOKEN and consumes Apify credits per contact searched and per number found, plus the buyer's own provider credits.

Parametersemailcontactsfull_namemobile_onlylinkedin_urlmax_contactscompany_domainmax_charge_usdprovider_ordermax_provider_credits

Version history

2
  1. v1.0.2LatestNov 5, 2026
  2. v1.0.1Oct 19, 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