Skip to main content
Glama
generect

Generect Live API MCP Server

Official
by generect
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

Related Servers

Alternatives to Generect Live API MCP Server

No user-submitted related servers found.

    Related Servers

    • leads-mcp

      AtomicIntuition
      A
      license
      A
      quality
      D
      maintenance
      Lead generation MCP server for AI agents. Find emails, verify contacts, enrich profiles, and search prospects using Hunter.io, Apollo.io, and Abstract API.
      8
      15 npm
      MIT
    • scrapercity-cli by scrapercity

      scrapercity-cliofficial

      scrapercity
      A
      license
      B
      quality
      A
      maintenance
      B2B 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.
      25
      892 npm
      1
      MIT

    • LeadClaw

      leadbay
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP 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

    • mcp-server-apollo

      borgels
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Apollo.io B2B data discovery and enrichment, enabling company search, people search, contact enrichment, and organization firmographics through Apollo's REST API.
      8
      Apache 2.0

    • Vibe Prospecting

      explorium-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      An 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.
      258
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have clearly distinct resource/action boundaries, especially between counting, previewing, searching, and enriching. The main confusion is get_lead_by_url, which is explicitly an alias of enrich_lead, plus some conceptual overlap between resolve_profile and enrich_lead.

    Naming Consistency4/5

    The set is mostly consistent snake_case verb_noun naming (search_leads, enrich_company, create_webhook), which is easy to scan. Minor deviations are health as a bare noun and get_lead_by_url, whose get_ prefix is semantically inconsistent with the enrich_ family.

    Tool Count3/5

    At 21 tools the surface is somewhat heavy, though the domain is broad: search, enrichment, email, phone, bulk jobs, webhooks, and account health. The redundant alias get_lead_by_url and the five webhook tools push it beyond the ideal tightly scoped range.

    Completeness4/5

    The surface covers the core lead-generation lifecycle: counting, searching, previewing, enriching, email generation/validation, phone lookup, bulk jobs, and webhook management. Minor gaps remain around asynchronous job management, such as canceling or listing bulk jobs, but most workflows are workable.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources