Generect Live API MCP Server
OfficialRelated Servers
Alternatives to Generect Live API MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceLead generation MCP server for AI agents. Find emails, verify contacts, enrich profiles, and search prospects using Hunter.io, Apollo.io, and Abstract API.813 npmMIT

scrapercity-cliofficial
AlicenseBqualityAmaintenanceB2B lead generation MCP server with 20+ lead generation tools - Apollo scraping, Google Maps, email finder, email validator, mobile finder, skip trace, ecommerce store data, and more.2530 npm1MIT- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI agents to discover and qualify B2B leads from Leadbay's knowledge base, with tools for lead research, enrichment, and outreach logging.MIT
- FlicenseAqualityCmaintenanceMCP server for real-time public-web lead research without search API keys, using Google Maps and web search engines with LLM-based extraction, crawling, and local lead storage/export.8-
- AlicenseAqualityCmaintenanceMCP server for Apollo.io B2B data discovery and enrichment, enabling company search, people search, contact enrichment, and organization firmographics through Apollo's REST API.8Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server providing real-time access to comprehensive B2B company and contact data for lead generation and business intelligence. It enables AI tools to search firmographics, discover key contacts, and automate personalized outreach workflows.55MIT
TDQS
Scored across 17 tools
Tool purposes are mostly distinct: count/search/preview/enrich/generate/validate/find each map to different operations, and free vs billable tools are clearly separated. The main ambiguity is get_lead_by_url, which is explicitly an alias for enrich_lead and creates redundancy.
Names follow a predictable snake_case verb_noun pattern like count_leads, search_companies, enrich_lead, and generate_email. The exceptions are the bare noun 'health' and the more awkward alias get_lead_by_url, but the overall convention is consistent.
At 17 tools, the set sits in the heavy/borderline range, though most tools map to distinct API operations. The redundant get_lead_by_url alias and the peripheral health tool could be trimmed without losing core functionality.
The surface covers the main lead-generation lifecycle: count, preview, search, enrich, resolve profiles, email/phone lookup, bulk jobs, webhooks, and billing. Minor gaps exist—no preview_companies counterpart and no bulk-job cancellation—but core workflows have no dead ends.