Influencer Lead List Builder MCP Server
Related Servers
Alternatives to Influencer Lead List Builder MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables matching influencers to their talent agencies and agencies to their public creator rosters through an Apify actor.192 npmMIT
- AlicenseAqualityAmaintenanceEnables pushing enriched leads into Instantly or Smartlead campaigns with ICP score gating, deduplication, and dry-run previews via an Apify actor.187 npmMIT
- AlicenseAqualityAmaintenanceEnables B2B lead generation through Apify's Prospect Engine actor, supporting company enrichment, job discovery, contact finding, and full ICP-gated outreach workflows.176 npmMIT
- AlicenseAqualityAmaintenanceEnables building targeted company lists from live job boards or SEC filings via the Apify actor, supporting role keywords, locations, and filing phrases.164 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to pull TikTok creator profiles with published contact emails and social links, uncover the contact email behind YouTube channels alongside their video stats, and fetch transcripts from TikTok, Instagram, YouTube and X videos. Authentication uses your own Apify token, with usage billed directly to your Apify account.MIT

actors-mcp-serverofficial
AlicenseAqualityAmaintenanceUse 3,000+ pre-built cloud tools from Apify, known as Actors, to extract data from websites, e-commerce, social media, search engines, maps, and more1230,525 npm14,092MIT
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.