actors-mcp-serverofficial
A
licenseA
qualityA
maintenanceUse 3,000+ pre-built cloud tools from Apify, known as Actors, to extract data from websites, e-commerce, social media, search engines, maps, and more
10
11,756 npm
7,618
MIT
Influencer Lead List Builder MCP Server
by mambalabsdev
Allows discovering and evaluating Apple Podcasts shows as creator leads by keyword or handle.
Allows discovering and evaluating Instagram influencer profiles by keyword or handle, including profile details, bio links, and follower counts.
Allows discovering and evaluating Pinterest influencer profiles by keyword or handle for lead list building.
Allows discovering and evaluating Threads influencer profiles by keyword or handle for lead list building.
Allows discovering and evaluating TikTok influencer profiles by keyword or handle, including profile details and follower counts for lead list building.
Allows discovering and evaluating Twitch influencer profiles by keyword or handle, with optional official Twitch API reads when credentials are provided.
Allows discovering and evaluating YouTube influencer profiles by keyword or handle, reading channel details and audience size for lead list building.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Influencer Lead List Builder MCP Serverbuild an influencer lead list for vegan food bloggers with contact emails"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Influencer Lead List Builder MCP Server
MCP server for the Mamba Labs Influencer Lead List Builder actor on Apify.
Discovery, the profile read, and the link check in one run, on one flat row per creator.
Install
npx -y @mambalabsdev/mcp-creator-lead-list-all-in-oneClaude Desktop
{
"mcpServers": {
"mamba-creator-lead-list-all-in-one": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-creator-lead-list-all-in-one"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}Get an Apify token at console.apify.com/account/integrations.
Related MCP server: Web Intelligence MCP Server
Tool
build_influencer_lead_list
Keywords or handles in, a finished influencer lead list with contact details out.
Input | Type | Required | Notes |
| array | no | Search phrases, one per line, for example "budget travel" or "meal prep coach". Each keyword is searched on each platform. Use |
| string | no | Loads a curated set of search keywords for the niche (about 60 per niche, measured in the September 2026 pre-research). |
| integer | no | How many keywords from the niche set to search. 1 to 60. Default |
| array | no | One per line. A profile URL on any supported platform (https://www.tiktok.com/@name, https://www.instagram.com/name/, https://www.youtube.com/@name, a Pinterest, Twitch, or Threads profile, an Apple Podcasts show. |
| array | no | Which platforms to search, and which platforms a bare @handle is looked up on. A full profile URL carries its own platform and ignores this. Supported: TikTok, Instagram, YouTube, Pinterest, Twitch, Threads, and. |
| integer | no | Cap per search. Search engines honor the site: filter for the first page or two only, so 20 to 30 per keyword with more keywords beats deep paging. Default |
| integer | no | Hard cap on rows returned, so a broad niche cannot run away. Default |
| integer | no | Drop creators whose follower count is known and below this. A creator whose count the search did not show is kept, so a later profile read can fill it. Default |
| integer | no | Drop creators whose follower count is known and above this. Default |
| boolean | no | Launch scope is US creators. A row whose country_guess is a known non US country is returned as an error row saying so. Rows with no country signal are kept. Uncheck to keep every country. Default |
| boolean | no | Off by default. On: discovery and profile only. The link-in-bio page is never fetched, so no links-checked, browser-render, website-scan, or agency-match event is charged and the links, newsletter, and sells columns. Default |
| boolean | no | Off by default. Some link-in-bio pages (Stan Store, linkin.bio, Typeform shells) return an empty shell to a plain fetch and are classified unknown_fetch_failed. Turn this on to render them in a headless browser.. Default |
| boolean | no | Off by default. When on, a model reads the rule classifier's evidence and rules on each row. Runs only with your own key in |
| string | no | Which API the key belongs to. Default |
| string | no | Your own model API key. Used only when |
| boolean | no | Off by default. For creators with their own website (not a link-in-bio page), reads the home, contact, and about pages and the footer for an email and records where it was found. Charged per creator scanned (event. Default |
| boolean | no | Matches the domain of a manager or business email against the bundled talent agency list and fills agency_name, agency_domain, and agency_match_method. Charged per matched row (event agency-match). Default |
| boolean | no | On by default. A profile fetch that comes back as a bot detection page is retried once over the residential proxy. On Instagram the bio, bio link, and following are read from the profile page over residential when. Default |
| integer | no | Rows fetched at once. Leave empty for the measured per platform default; the measurement is in the README. Higher is faster and, above the measured point, loses rows. |
| string | no | Leave empty for the default. sub_actors calls the Influencer Finder, the Influencer Profile Scraper, and the Link in Bio Scraper and Newsletter Detector by Actor ID as runs on your account, so each stage bills its. |
| string | no | Optional. Your own registered Twitch application client id. With |
| string | no | Optional. An app access token for your Twitch client id (client credentials flow). Used only for Twitch reads, never stored or logged. |
Nothing is required. Influencer Lead List Builder answers a run with no usable input with a row carrying row_status and error_reason rather than failing, and the tool mirrors that.
Pricing
Influencer Lead List Builder is pay per event on Apify. Every price below is flat across the FREE, BRONZE, SILVER, and GOLD tiers.
Event | Charged for | Price | Fires when |
| Actor start | $0.002 | Once per run, on start. Covers the run overhead. |
| Creator found | $0.007 | Once per creator row returned by keyword or niche discovery with a handle and a profile URL. A search that returns nothing charges nothing. |
| Profile read | $0.006 | Once per profile row where the public profile page was read and at least the follower count or the bio came back. A private, missing, or blocked profile returns a labeled error row and does not charge. |
| Links checked | $0.008 | Once per creator whose bio link or link-in-bio page was fetched and classified. A creator with no bio link returns newsletter_status none from the bio alone and does not charge this event. |
| Browser render | $0.004 | Once per page rendered in the headless browser because the plain fetch did not return readable content (Stan Store, linkin.bio, Typeform shells) and the rendered page came back readable: 120 characters of visible text or 3 links off the page's host, and no block page. A render that returns the same empty shell is not charged, and a charged render always reaches the classifier. Only when the option is on. Priced to cover the browser compute. |
| Website scan | $0.005 | Once per creator whose own website (not a link-in-bio page) was scanned for an email on the home, contact, about, and footer. Only when the add-on is on. |
| Agency match | $0.003 | Once per creator row where a manager or agency email domain was matched against the bundled agency list and an agency name came back. |
| Instagram bio fetch | $0.01 | Once per Instagram profile row when the bio, bio link, and following were not on the embed widget or the datacenter API and the profile page was read over the residential proxy and came back readable. Only when escalate_on_block is on. Never on the embed or datacenter reads, never on another platform, never on a blocked page, and never on an error row. |
Reading the output
Every row carries row_status and error_reason. A creator the actor could not read comes back as a row saying why, not as a gap in the list, so an absence is readable rather than inferred. Filter on row_status before loading a table.
Actor
Actor ID KnmByszcv135yM30G. The wrapper calls the actor by that immutable ID rather than by its Store slug, so a Store rename never breaks it.
Suite
Actor | Actor ID | MCP server |
| ||
| ||
| ||
| ||
|
Built by Mamba Labs.
Available Tools
1 toolbuild_influencer_lead_listBuild an Influencer Lead List End to EndARead-onlyIdempotent
Runs the three stages of the suite in one call: find creators by keyword or curated niche, read each profile, then follow the link in bio page. Returns one flat row per creator carrying handle, profile URL, display name, follower count, a stable creator_id and the method that produced it, the public business email, a manager email, a matched talent agency, newsletter status and the platform behind it, and what the creator sells. Start from keywords or a niche to discover creators, or hand it handles you already hold to skip discovery. Skipping the link check stops after the profile read. Every row carries row_status and error_reason, and a creator dropped by the country filter says so rather than disappearing. Charges $0.002 per run, then $0.007 per creator found, $0.006 per profile read, and $0.008 per link check, plus $0.004 per headless browser render, $0.005 per website email scan, $0.003 per agency match, and $0.01 per Instagram bio fetch when those steps run. The AI check uses your own Anthropic or OpenAI key and is billed by them. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Leave empty for the default. sub_actors calls the Influencer Finder, the Influencer Profile Scraper, and the Link in Bio Scraper and Newsletter Detector by Actor ID as runs on your account, so each stage bills its own events and its own actor-start. in_process runs the same three stages inside this actor and charges the same stage events here. A complete row costs $0.021 either way, plus the add-ons you turn on. | |
| niche | No | Loads a curated set of search keywords for the niche (about 60 per niche, measured in the September 2026 pre-research). `max_keywords_per_niche` caps how many are used. Leave as custom to search only your keywords. Default: "custom". | |
| handles | No | One per line. A profile URL on any supported platform (https://www.tiktok.com/@name, https://www.instagram.com/name/, https://www.youtube.com/@name, a Pinterest, Twitch, or Threads profile, an Apple Podcasts show page, or a Spotify show), or platform:@handle (tiktok:@name). A bare @handle needs `platforms` and is looked up on each listed platform. One entry is a single run; a list is a batch. Duplicates are removed before any fetch. | |
| us_only | No | Launch scope is US creators. A row whose country_guess is a known non US country is returned as an error row saying so. Rows with no country signal are kept. Uncheck to keep every country. Default: true. | |
| ai_check | No | Off by default. When on, a model reads the rule classifier's evidence and rules on each row. Runs only with your own key in `ai_api_key`; the actor never uses a Mamba Labs key and never logs yours. Default: false. | |
| keywords | No | Search phrases, one per line, for example "budget travel" or "meal prep coach". Each keyword is searched on each platform. Use `niche` instead to load a curated keyword set. | |
| platforms | No | Which platforms to search, and which platforms a bare @handle is looked up on. A full profile URL carries its own platform and ignores this. Supported: TikTok, Instagram, YouTube, Pinterest, Twitch, Threads, and podcasts. Not X, not Facebook pages, not LinkedIn. | |
| ai_api_key | No | Your own model API key. Used only when `ai_check` is on. Never stored, logged, or written to a row. | |
| batch_size | No | Rows fetched at once. Leave empty for the measured per platform default; the measurement is in the README. Higher is faster and, above the measured point, loses rows. | |
| skip_links | No | Off by default. On: discovery and profile only. The link-in-bio page is never fetched, so no links-checked, browser-render, website-scan, or agency-match event is charged and the links, newsletter, and sells columns stay null. Default: false. | |
| ai_provider | No | Which API the key belongs to. Default: "anthropic". | |
| follower_max | No | Drop creators whose follower count is known and above this. Default: 500000. | |
| follower_min | No | Drop creators whose follower count is known and below this. A creator whose count the search did not show is kept, so a later profile read can fill it. Default: 5000. | |
| max_creators | No | Hard cap on rows returned, so a broad niche cannot run away. Default: 200. | |
| match_agencies | No | Matches the domain of a manager or business email against the bundled talent agency list and fills agency_name, agency_domain, and agency_match_method. Charged per matched row (event agency-match). Default: true. | |
| twitch_app_token | No | Optional. An app access token for your Twitch client id (client credentials flow). Used only for Twitch reads, never stored or logged. | |
| twitch_client_id | No | Optional. Your own registered Twitch application client id. With `twitch_app_token` the Twitch reads use the official Helix API instead of the public web endpoint. Never a Mamba Labs credential. | |
| escalate_on_block | No | On by default. A profile fetch that comes back as a bot detection page is retried once over the residential proxy. On Instagram the bio, bio link, and following are read from the profile page over residential when the embed and the datacenter API did not carry them, and a page that comes back readable charges instagram-bio-fetch ($0.010). Uncheck it to never pay that event: a blocked profile then returns a labeled error row, and Instagram rows keep an empty bio and bio link on about half of the reads. Default: true. | |
| max_keywords_per_niche | No | How many keywords from the niche set to search. 1 to 60. Default: 10. | |
| scan_website_for_email | No | Off by default. For creators with their own website (not a link-in-bio page), reads the home, contact, and about pages and the footer for an email and records where it was found. Charged per creator scanned (event website-scan). Default: false. | |
| render_unreadable_pages | No | Off by default. Some link-in-bio pages (Stan Store, linkin.bio, Typeform shells) return an empty shell to a plain fetch and are classified unknown_fetch_failed. Turn this on to render them in a headless browser. Charged per page rendered (event browser-render) to cover the browser compute. Default: false. | |
| max_creators_per_keyword | No | Cap per search. Search engines honor the site: filter for the first page or two only, so 20 to 30 per keyword with more keywords beats deep paging. Default: 20. |
TDQS
A4.4/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the operation as read-only, idempotent, and non-destructive, and the description reinforces 'Read only.' It adds substantial behavioral detail beyond the annotations: exact per-run and per-stage pricing, APIFY_TOKEN requirement, AI-check key ownership, country-filter error rows, row_status/error_reason behavior, and conditional add-on charges. This gives the agent a strong model of side effects and costs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is long but information-dense, and the complexity of a 22-parameter end-to-end pipeline justifies the length. It front-loads the action and output shape before moving to cost, auth, and edge-case behavior. It is not perfectly scannable as a single paragraph, but it avoids filler and every sentence adds useful guidance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema and no sibling tools, the description covers what an agent needs to call it correctly: the pipeline stages, output row fields, row_status/error_reason guarantees, cost model, token/key requirements, and skip options. Nothing critical for invoking the tool is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage across all 22 parameters, so the structured schema already carries the parameter-level meaning. The description adds high-level workflow and pricing context but does not need to restate individual parameter semantics. A baseline of 3 is appropriate since the schema is doing the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific composite action—running all three stages (discovery, profile read, link-in-bio follow) in one call—and specifies exactly what is returned per creator. It also clearly distinguishes intended entry paths: keywords, curated niche, or pre-existing handles. This goes well beyond a restatement of the tool name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives concrete usage context: start with keywords or a niche to discover, or pass handles to skip discovery, and it explains the effect of skipping the link check. There are no sibling tools listed, so there is no alternative to contrast, but the guidance is clear enough that an agent can decide how to invoke the tool appropriately.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
build_influencer_lead_list
TDQS
A4.4/5.0
Scored across 1 tool
Disambiguation5/5
There is only one tool, so there is no possibility of selecting the wrong tool. The tool itself handles multiple modes (discovery, profile read, link check) internally, but these are not separate selectable operations.
Naming Consistency5/5
The single tool name follows a clear verb_noun pattern: build_influencer_lead_list. With only one tool, there is no inconsistency to evaluate, but the name accurately conveys the action and target.
Tool Count3/5
The server provides exactly one tool, which feels thin for a typical MCP server. Although the single tool is comprehensive and covers the entire lead-list-building pipeline, a 1-2 tool server is borderline per the calibration guidelines.
Completeness5/5
The tool fully covers the domain of influencer lead list building: discovery by keyword or niche, profile reads, link-in-bio checks, and enrichment with emails, agency matches, and platform data. Options to skip stages provide flexibility, and no obvious operations are missing.
Maintenance
ActivityMaintained
ResponsivenessNo issues
Related MCP Connectors
Manage 230M+ influencers, track campaigns, and access real-time CIMS analytics via AI agents
Find and analyze influencers with creator search, lookalikes, profiles, posts, and transcripts.
Extract emails and phones from any website via Apify.
Run Signal Lab Apify Actors for price tracking, keywords, RAG, transcripts, Reddit, jobs, and menus.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with real-time web capabilities including live search results, markdown web scraping, business lead generation, and detailed company information. It enables agents to bypass knowledge cutoffs by accessing current web data through a monetized Apify Actor.-
- AlicenseAqualityAmaintenanceEnables pushing enriched leads into Instantly or Smartlead campaigns with ICP score gating, deduplication, and dry-run previews via an Apify actor.183 npmMIT
- AlicenseAqualityAmaintenanceEnables building targeted company lists from live job boards or SEC filings via the Apify actor, supporting role keywords, locations, and filing phrases.137 npmMIT