Skip to main content
Glama
Influencer Lead List Builder MCP Server

Influencer Lead List Builder MCP Server

Related Servers

Alternatives to Influencer Lead List Builder MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables pushing enriched leads into Instantly or Smartlead campaigns with ICP score gating, deduplication, and dry-run previews via an Apify actor.
      1
      97 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables B2B contact enrichment and account signals through Apify Actors: finding new hires and their previous employers, detecting company email formats, discovering lookalike companies, listing decision makers, resolving emails from LinkedIn profiles, and searching a people database by title, seniority, and country. Supports per-call spend caps, free count/market modes, and returns status-annotated rows plus dataset links.
      6
      82 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables exporting public GitHub followers and following lists as flat rows with profile details and completeness reports via an Apify actor. It accepts usernames or profile URLs and supports follower, following, or both lists with configurable result limits.
      1
      331 npm
      MIT

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation4/5

    With a single exposed tool there is no internal overlap or risk of misselection. However, the description repeatedly points to companion 'single stage' tools that are not in the set, creating confusion about what is actually callable.

    Naming Consistency5/5

    The lone tool uses a clear snake_case verb_noun pattern (build_influencer_lead_list) that matches the server's domain. With only one tool there is no possibility of convention drift.

    Tool Count2/5

    A single monolithic tool bundles three distinct stages (discovery, profile read, link check) that the description itself admits are cheaper to run individually, yet no per-stage tools are exposed. One tool is too thin for the advertised 'suite' scope.

    Completeness2/5

    The surface has clear dead ends: the description references `contribute_to_shared_pool` and single-stage tools that do not exist as callables. There is also no way to inspect run status, retrieve results by run ID, or manage the shared-pool opt-out programmatically.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data