Mcp Mobile Phone Waterfall Orchestrator

com.mambabuilt由 mambabuilt.com 發布v1.0.2更新於 Nov 7, 2026

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

已驗證STDIO僅桌面資料與分析商業與電商

概覽

AI 產生的概覽

透過 Apify 執行器串接你自己的 Prospeo、Lusha、ContactOut 與 FullEnrich 金鑰，為聯絡人清單查找手機號碼。

可以做什麼
  • 為單一聯絡人或整批聯絡人查找手機號碼，可用姓名、公司網域、LinkedIn 連結或電子郵件作為識別
  • 依指定順序逐一呼叫你自己的手機號碼資料供應商，直到其中一家回傳號碼
  • 每個聯絡人回傳一列結果，包含 E.164 格式號碼、線路類型、國家、供應商提供的勿擾標記，以及消耗的供應商額度
  • 支援僅手機號碼、最大聯絡人數、最大供應商額度、最高美元費用等限制
適用情境
適合已擁有 Apify 與手機號碼資料供應商帳號、希望讓助理一步為聯絡人清單補齊手機號碼，且不想把金鑰貼進對話的情況。
執行需求
透過 npx 以 stdio 在本機執行（需要 Node.js）。必須提供 APIFY_TOKEN；PROSPEO_API_KEY、LUSHA_API_KEY、CONTACTOUT_API_KEY、FULLENRICH_API_KEY 為選用，從伺服器環境變數讀取。需要連線至 Apify 與各供應商的網路。
安裝前請注意
執行會產生費用：Apify 依啟動事件、曾呼叫供應商的聯絡人數以及查到的號碼數計費，各供應商也會在你的金鑰上扣除自身額度；未設定任何供應商金鑰的執行仍會收取啟動費。僅 Prospeo 路徑曾在真實金鑰上驗證，Lusha、ContactOut 與 FullEnrich 步驟尚未驗證。聯絡人識別資料（包含 LinkedIn 連結）會傳送給第三方供應商。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Mcp Mobile Phone Waterfall Orchestrator，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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.

來源：README.md，提交 d25569a

工具

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.

輸入參數emailcontactsfull_namemobile_onlylinkedin_urlmax_contactscompany_domainmax_charge_usdprovider_ordermax_provider_credits

版本歷史

2
  1. v1.0.2最新Nov 5, 2026
  2. v1.0.1Oct 19, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分