LeadFuze-MCP-Server
Related Servers
Alternatives to LeadFuze-MCP-Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables multi-provider waterfall data enrichment for B2B prospects, firmographics, and verified decision-maker corporate emails via MCP.-

Getlead MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables finding B2B leads with verified work emails, finding and verifying email addresses, and running cold email outreach from any MCP client.1MIT
FullEnrich MCPofficial
AlicenseNot gradedqualityCmaintenanceEnables 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.14MIT
Signaliz MCPofficial
FlicenseNot gradedqualityDmaintenanceProvides MCP clients with 60+ APIs for B2B data enrichment, lead generation, email verification, company intelligence, and agentic GTM workflows.-
Skrapp MCPofficial
FlicenseNot gradedqualityBmaintenanceEnables MCP clients to find and verify professional emails, look up phone numbers, search and enrich companies, and manage lists through plain-language workflows.-
Evascrape MCP serverofficial
AlicenseAqualityBmaintenanceEnables MCP clients to find business leads with email addresses and other details from Google Maps, Apollo.io, and LinkedIn, with asynchronous extraction, job status checks, cost estimates, and structured downloads.744 npmMIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: enrich_by_email and enrich_by_linkedin both enrich contact data but use different input types (email vs. LinkedIn URL), while validate_email performs a separate validation function. There is no ambiguity or overlap in their core operations.
All tool names follow a consistent verb_noun pattern with snake_case (enrich_by_email, enrich_by_linkedin, validate_email). The naming is predictable and readable across the set.
Three tools is reasonable for a lead enrichment and validation server, though it feels slightly minimal. Each tool earns its place, but the scope could potentially support a few more related operations without being overburdened.
The tools cover key enrichment and validation workflows for lead data, with no obvious dead ends. Minor gaps might include bulk operations or additional data sources, but agents can effectively work with the provided surface for common use cases.