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 分