com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator
NPM · @MAMBALABSDEV/MCP-MOBILE-PHONE-WATERFALL-ORCHESTRATOR
Find mobile phone numbers by chaining your own Prospeo, Lusha, ContactOut, and FullEnrich keys.
Available components
Last scanned (9 hours ago)
Scores higher than 40% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 463 tokens (~463/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 19 Oct 26 58
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed npm/@mambalabsdev/mcp-mobile-phone-waterfall-orchestrator@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_mobile_phone Find mobile phone ~463
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_domain | string | – | Single contact shortcut: company domain. |
| contacts | array | – | People to look up. Give each as many identifiers as you hold. |
| string | – | Single contact shortcut: email. | |
| full_name | string | – | Single contact shortcut: full name. |
| linkedin_url | string | – | Single contact shortcut: LinkedIn profile URL, never opened by the actor. |
| max_charge_usd | string | – | 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. |
| max_contacts | string | – | Ceiling on how many contacts this run processes. |
| max_provider_credits | string | – | Cap on the provider credits this run may spend on the buyer's own accounts. Remaining contacts are skipped, uncharged. Strongly recommended. |
| mobile_only | string | – | 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. |
| provider_order | array | – | Providers in call order. Default prospeo, lusha, contactout, fullenrich. A provider with no key is skipped and reported. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator server?
com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-mobile-phone-waterfall-orchestrator. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-mobile-phone-waterfall-orchestrator
claude mcp add com-mambabuilt-mcp-mobile-phone-waterfall-orches -- npx -y @mambalabsdev/mcp-mobile-phone-waterfall-orchestrator
What is the com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator server?
com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator is listed in the public MCP registry as com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator. Find mobile phone numbers by chaining your own Prospeo, Lusha, ContactOut, and FullEnrich keys. This page covers its npm package (@mambalabsdev/mcp-mobile-phone-waterfall-orchestrator).
Is the com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator server safe to use?
com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator server expose?
com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator exposes 1 tool: find_mobile_phone. Their descriptions and schemas cost roughly 463 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator server still maintained?
com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator server under?
com.mambabuilt/mcp-mobile-phone-waterfall-orchestrator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.