Mobile Phone Waterfall MCP Server
Related Servers
Alternatives to Mobile Phone Waterfall MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables finding and verifying work emails for contacts through a waterfall of provider keys, with per-provider cost attribution and verification after each finder.1100 npmMIT
- 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

FullEnrich MCPofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to search B2B people and companies, enrich contacts with verified emails and mobile phone numbers via waterfall enrichment across 25+ providers, and export results as CSV or JSON. Supports prospecting, org mapping, candidate sourcing, and outreach workflows through OAuth-authenticated remote access from any MCP-compatible client.10MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to look up a person’s phone number by name and current employer, LinkedIn URL, or email, returning line type, confidence grade, and person/company context.7 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-
openpeoplerouterofficial
AlicenseAqualityBmaintenanceEnables 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.121Apache 2.0
TDQS
Scored across 1 tool
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.
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.
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.
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.