Skip to main content
Glama
leadfuze

LeadFuze-MCP-Server

by leadfuze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to LeadFuze-MCP-Server

No user-submitted related servers found.

    Related Servers

    • Signaliz MCP by signaliz

      Signaliz MCPofficial

      signaliz
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP clients with 60+ APIs for B2B data enrichment, lead generation, email verification, company intelligence, and agentic GTM workflows.
      -

    • fetchcraft-mcp

      emily397
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables B2B research by finding verified work emails, extracting contacts, detecting tech stacks, and profiling DNS and SaaS, all through a suite of MCP tools.
      -

    • 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
      4 npm
      MIT

    • person-enrichment

      Br0ski777
      A
      license
      Not graded
      quality
      B
      maintenance
      Enriches person profiles from email addresses, returning full name, job title, company, social links, and location. Works as a drop-in replacement for Apollo person enrichment at lower cost.
      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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources