Influencer Lead List Builder MCP Server
Related Servers
Alternatives to Influencer Lead List Builder MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables matching influencers to their talent agencies and agencies to their public creator rosters through an Apify actor.164 npmMIT
- AlicenseAqualityBmaintenanceEnables pushing enriched leads into Instantly or Smartlead campaigns with ICP score gating, deduplication, and dry-run previews via an Apify actor.197 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.682 npmMIT
- AlicenseAqualityBmaintenanceEnables B2B lead generation through Apify's Prospect Engine actor, supporting company enrichment, job discovery, contact finding, and full ICP-gated outreach workflows.194 npmMIT
- AlicenseAqualityBmaintenanceEnables building targeted company lists from live job boards or SEC filings via the Apify actor, supporting role keywords, locations, and filing phrases.176 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.1331 npmMIT
TDQS
Scored across 1 tool
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.
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.
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.
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.