Work Email Waterfall MCP Server
Related Servers
Alternatives to Work Email Waterfall MCP Server
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityCmaintenanceEnables multi-provider waterfall enrichment of B2B prospect data, combining firmographic details and verified decision-maker emails with automated fallback and deliverability filtering.8-- AlicenseNot gradedqualityBmaintenanceFinds, filters, and verifies local-business leads on demand; every returned email carries a verification receipt (verifier, verdict, timestamp). Credit-based with per-key spend budgets; 25 free validated leads at signup.MIT
- AlicenseAqualityDmaintenanceFinds and verifies business email addresses using DNS/SMTP verification and web scraping, with no external API costs.516 npm11MIT
- FlicenseNot gradedqualityBmaintenanceEnables multi-provider waterfall data enrichment for B2B prospects, firmographics, and verified decision-maker corporate emails via MCP.8-
- AlicenseNot gradedqualityBmaintenanceFind professional email addresses from name + company domain. Tests 15+ patterns against MX records with confidence scoring, with pay-per-call via x402.MIT
- FlicenseNot gradedqualityBmaintenanceEnables autonomous B2B lead enrichment through a waterfall cascade and technographic stack verification, producing structured output dossiers for AI agents and enterprise pipelines.8-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another. The tool's purpose is clearly defined and distinct.
The tool name 'find_work_email' follows a clean verb_noun pattern. While consistency is trivially met with a single tool, the name is descriptive and predictable.
A single-tool server feels thin, but for this niche operation (finding work emails via provider chaining) it may suffice. However, separate tools for key management or provider configuration would improve structure.
The tool covers the full workflow: accepting multiple contact identifiers, running providers, verifying results, handling missing keys, providing per-contact and summary rows, and returning JSON. No obvious gaps exist within its stated scope.