Skip to main content
Glama
Mobile Phone Waterfall MCP Server

Mobile Phone Waterfall MCP Server

Mobile Phone Waterfall MCP Server

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

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

Related MCP server: Work Email Waterfall MCP Server

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.

Available Tools

1 tool
find_mobile_phoneFind mobile phoneA
Read-only

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

Inputs: email, contacts, full_name, mobile_only, +6 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool in the set, there is no possibility of confusing it with another tool or misselecting between overlapping purposes. The tool's purpose (waterfall phone-number lookup) is clearly stated and unambiguous.

    Naming Consistency5/5

    The lone tool, find_mobile_phone, follows a clear verb_noun snake_case convention. With one tool there is no risk of inconsistent conventions, though the pattern can only be assessed trivially.

    Tool Count3/5

    The server targets a narrow, single-purpose operation, so one tool is defensible, but the surface is thin: a single tool leaves no room for adjacent operations like checking run status, listing past runs, or validating numbers. It sits at the borderline of 'feels thin' rather than being an extreme mismatch.

    Completeness3/5

    The core lookup operation appears fully specified (E.164 output, line type, DNC flag, provider attribution, spend, error-with-run-ID handling). However, obvious lifecycle operations are absent: no tool to retrieve or poll a prior run's status/results and no way to inspect or configure provider order or credits, so agents hit dead ends on anything beyond a single fire-and-forget call.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enriches person profiles from email addresses, returning full name, job title, company, social links, and location. Works as a drop-in replacement for Apollo person enrichment at lower cost.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables finding and verifying work emails for contacts through a waterfall of provider keys, with per-provider cost attribution and verification after each finder.
      1
      281 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables multi-provider waterfall enrichment of B2B prospect data, combining firmographic details and verified decision-maker emails with automated fallback and deliverability filtering.
      8
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables people and company discovery, enrichment, identity resolution, and contact finding through unified MCP tools, with optional provider endpoint catalog access using your own API keys.
      12
      9
      Apache 2.0