com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator
Find mobile phone numbers by chaining your own Prospeo, Lusha, ContactOut, and FullEnrich keys.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@mambalabsdev/mcp-mobile-phone-waterfall-orchestratorclaude mcp add mcp-mobile-phone-waterfall-orchestrator -e 'APIFY_TOKEN=<your apify_token>' -e 'PROSPEO_API_KEY=<your prospeo_api_key>' -e 'LUSHA_API_KEY=<your lusha_api_key>' -e 'CONTACTOUT_API_KEY=<your contactout_api_key>' -e 'FULLENRICH_API_KEY=<your fullenrich_api_key>' -- npx -y @mambalabsdev/mcp-mobile-phone-waterfall-orchestrator@1.0.1
{
"mcpServers": {
"mcp-mobile-phone-waterfall-orchestrator": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-mobile-phone-waterfall-orchestrator@1.0.1"
],
"env": {
"APIFY_TOKEN": "<your apify_token>",
"PROSPEO_API_KEY": "<your prospeo_api_key>",
"LUSHA_API_KEY": "<your lusha_api_key>",
"CONTACTOUT_API_KEY": "<your contactout_api_key>",
"FULLENRICH_API_KEY": "<your fullenrich_api_key>"
}
}
}
}
Environment variables
APIFY_TOKENrequired secret Apify API token from https://console.apify.com/account/integrationsPROSPEO_API_KEYsecret Optional. Your Prospeo API key.LUSHA_API_KEYsecret Optional. Your Lusha API key (V3).CONTACTOUT_API_KEYsecret Optional. Your ContactOut API token.FULLENRICH_API_KEYsecret Optional. Your FullEnrich API key.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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 providers_not_live_verified. No key is stored.
Tool
| Tool | What it does |
|---|---|
find_mobile_phone | Looks up mobile numbers for a list of contacts on your own provider keys |
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 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.
Frequently asked questions
What is com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator?
Find mobile phone numbers by chaining your own Prospeo, Lusha, ContactOut, and FullEnrich keys.
How do I install com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator?
It runs on your machine. In Claude Code: claude mcp add mcp-mobile-phone-waterfall-orchestrator -e 'APIFY_TOKEN=<your apify_token>' -e 'PROSPEO_API_KEY=<your prospeo_api_key>' -e 'LUSHA_API_KEY=<your lusha_api_key>' -e 'CONTACTOUT_API_KEY=<your contactout_api_key>' -e 'FULLENRICH_API_KEY=<your fullenrich_api_key>' -- npx -y @mambalabsdev/mcp-mobile-phone-waterfall-orchestrator@1.0.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator need an API key?
Yes. It expects APIFY_TOKEN, PROSPEO_API_KEY, LUSHA_API_KEY, CONTACTOUT_API_KEY, FULLENRICH_API_KEY, which you set in its configuration.
Is com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator?
It is published by mambalabsdev. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.