Work Email Waterfall MCP Server
Related Servers
Alternatives to Work Email Waterfall MCP Server
No user-submitted related servers found.
Related Servers
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-- AlicenseAqualityAmaintenanceEnables looking up mobile phone numbers for a list of contacts by chaining your own Prospeo, Lusha, ContactOut, and FullEnrich keys until a provider returns a number. Returns one row per contact with the number in E.164 format, line type, country, a Do Not Call flag where reported, and the provider credits spent.1156 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to find and verify B2B work emails for individuals or bulk lists, with deliverability checks, background job processing, and paginated result retrieval.MIT
- AlicenseNot gradedqualityDmaintenanceFinds, 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.538 npm12MIT
- AlicenseAqualityAmaintenanceEnables AI agents to verify email addresses with catch-all detection, search existing contacts by company domain, and, when no API key is present, provision a human-approved subscription and retrieve the key after payment.459 npmMIT
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.