A
licenseNot graded
qualityC
maintenanceAccount-based marketing enrichment for AI agents. Enriches people and companies from email, LinkedIn URL, or domain with cited multi-source fields.
42 npm
1
MIT
Mobile Phone Waterfall MCP Server
by mambalabsdev
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Mobile Phone Waterfall MCP Serverfind mobile phone numbers for jane@acme.com and tom@beta.io"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Tool
Tool | What it does |
| Looks up mobile numbers for a list of contacts on your own provider keys |
Related MCP server: person-enrichment
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 nothing.
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 toolfind_mobile_phoneFind mobile phoneARead-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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| No | Single contact shortcut: email. | ||
| contacts | No | People to look up. Give each as many identifiers as you hold. | |
| full_name | No | Single contact shortcut: full name. | |
| mobile_only | No | When true, a landline or VoIP number does not count as found and the chain moves on. Numbers with no reported line type are kept as unknown. Default true. | |
| linkedin_url | No | Single contact shortcut: LinkedIn profile URL, never opened by the actor. | |
| max_contacts | No | Ceiling on how many contacts this run processes. | |
| company_domain | No | Single contact shortcut: company domain. | |
| max_charge_usd | No | Optional cap on this run's Apify charges. The run stops before a charge that would pass it and keeps every row already paid for. | |
| provider_order | No | Providers in call order. Default prospeo, lusha, contactout, fullenrich. A provider with no key is skipped and reported. | |
| max_provider_credits | No | Cap on the provider credits this run may spend on the buyer's own accounts. Remaining contacts are skipped, uncharged. Strongly recommended. |
TDQS
A4.4/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations cover only the read/write and world-openness profile; the description adds the expensive details an agent needs: Apify credits plus the buyer's own provider credits, required APIFY_TOKEN, provider keys read from named environment variables, Do Not Call flag handling, and that a failed run is returned as an error with its run ID. LinkedIn URLs are explicitly never opened.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The return shape and cost profile are front-loaded, then auth, then failure behavior — a sensible ordering. It is long and runs several clauses per sentence, but almost every clause carries information an agent needs before calling.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description fully carries the return contract: one row per contact with E.164 number, line type, country, DNC flag, provider, credits spent, plus a run summary row. Cost, auth and failure semantics are all present, so nothing material is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so parameter documentation is already complete, including the mobile_only default and provider_order default. The description mostly restates those defaults rather than adding new parameter-level meaning, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource ('Find a mobile phone number for each contact') and goes further to explain the mechanism: a sequential waterfall across Prospeo, Lusha, ContactOut and FullEnrich. An agent knows exactly what the tool produces without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives clear operating context — the provider chain stops at the first hit, providers without keys are skipped, and with no keys set the run completes and charges nothing. There are no sibling tools to route against, so no exclusions are needed, but it also never states when this tool is the wrong choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
find_mobile_phone
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 issues
Related MCP Connectors
People-enrich: work email + phone, company & domain enrichment. Pay-per-call USDC, no key.
- PipecornOAuthcom.pipecorn
Search B2B companies and people, then find verified work emails and mobiles across 100+ providers.
Prospeo: Find, search, and enrich people and companies with verified emails and mobile numbers.
Wiza MCP — wraps the Wiza 'Individual Reveal' phone-lookup API (wiza.co)
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnriches 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
- AlicenseAqualityAmaintenanceEnables finding and verifying work emails for contacts through a waterfall of provider keys, with per-provider cost attribution and verification after each finder.1219 npmMIT
Waterfall Enrichmentofficial
FlicenseNot gradedqualityBmaintenanceEnables multi-provider waterfall enrichment of B2B prospect data, combining firmographic details and verified decision-maker emails with automated fallback and deliverability filtering.8-