Mcp Creator Lead List All In One

com.mambabuiltPublished by mambabuilt.comv1.2.1Updated Nov 7, 2026

Keywords or handles in, a finished influencer lead list with contact details out.

Overview

AI-generated overview

Builds influencer lead lists: one tool runs discovery, profile reads and link-in-bio checks on TikTok, Instagram, YouTube and more, returning one row per…

What you can do
  • Build a creator lead list from keywords, curated niches or handles across TikTok, Instagram, YouTube, Pinterest, Twitch, Threads and podcasts
  • Filter and cap results by follower range, per-keyword and total row limits, and US-only scope
  • Read each profile for follower count, bio and links, and classify the link-in-bio page for newsletter and store signals
  • Optionally scan creators' own websites for contact emails and match manager email domains against a bundled talent agency list
  • Return one flat row per creator with handle, profile URL, display name, follower count, creator_id and row_status/error_reason
When to use it
Use it when you need a ready influencer or creator outreach list with contact details for a niche, keyword set or known handles, rather than running discovery, profile reading and link checking as separate steps.
Requirements
Runs locally via npx (Node.js) as a stdio server, desktop only. Requires an Apify account and an APIFY_TOKEN environment variable; the underlying actor is billed per event on Apify. Optional inputs include your own model API key for ai_check and Twitch client id and app token for official Twitch reads.
Before you install
Pay-per-event Apify charges apply (creator found, profile read, links checked, browser render, website scan, agency match, Instagram bio fetch); set max_charge_usd to cap spend. The run contributes public records to a shared creator and agency pool by default; set contribute_to_shared_pool to false to write nothing. Optional ai_api_key and Twitch credentials are passed to the actor. Rows may include contact emails and agency matches, so handle them per privacy rules.

Installation

In SourceWeft

  1. Open Mcp Creator Lead List All In One in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Influencer Lead List Builder MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Creator Lead List All In One 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

bash
npx -y @mambalabsdev/mcp-creator-lead-list-all-in-one

Claude Desktop

json
{  "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.

Tool

build_influencer_lead_list

Keywords or handles in, a finished influencer lead list with contact details out.

InputTypeRequiredNotes
keywordsarraynoSearch 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.
nichestringnoLoads 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".
max_keywords_per_nicheintegernoHow many keywords from the niche set to search. 1 to 60. Default 10.
handlesarraynoOne 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.
platformsarraynoWhich 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.
max_creators_per_keywordintegernoCap 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.
max_creatorsintegernoHard cap on rows returned, so a broad niche cannot run away. Default 200.
follower_minintegernoDrop 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.
follower_maxintegernoDrop creators whose follower count is known and above this. Default 500000.
us_onlybooleannoLaunch 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.
skip_linksbooleannoOff 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 false.
render_unreadable_pagesbooleannoOff 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 false.
ai_checkbooleannoOff 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.
ai_providerstringnoWhich API the key belongs to. Default "anthropic".
ai_api_keystringnoYour own model API key. Used only when ai_check is on. Never stored, logged, or written to a row.
scan_website_for_emailbooleannoOff 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 false.
match_agenciesbooleannoMatches 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.
escalate_on_blockbooleannoOn 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 true.
batch_sizeintegernoRows 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.
modestringnoDefault in_process. 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.
twitch_client_idstringnoOptional. 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.
twitch_app_tokenstringnoOptional. An app access token for your Twitch client id (client credentials flow). Used only for Twitch reads, never stored or logged.
contribute_to_shared_poolbooleannoOn by default. Contributes the public records this run finds to a shared creator and agency pool that all users of this actor read from. Only public data already in the returned rows is sent, and a contribution is not charged. Set false to read the pool and write nothing. Default true.
max_charge_usdnumbernoOptional cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. Omit to rely on the maximum cost per run set in Apify.

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 every tier: FREE, BRONZE, SILVER, GOLD, PLATINUM, and DIAMOND.

EventCharged forPriceFires when
actor-startActor start$0.002Once per run, on start. Covers the run overhead.
apify-actor-startApify actor startnot chargedApify's synthetic start event. This actor prices its own actor-start event instead, so apify-actor-start is not charged on top of it.
creator-foundCreator found$0.007Once per creator row returned by keyword or niche discovery with a handle and a profile URL. A search that returns nothing charges nothing.
profile-readProfile read$0.006Once 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-checkedLinks checked$0.008Once 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-renderBrowser render$0.004Once 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-scanWebsite scan$0.005Once 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-matchAgency match$0.003Once 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-fetchInstagram bio fetch$0.01Once 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.

What this actor shares

The run contributes the records it finds to a shared creator and agency pool that all users of this actor read from. What one run finds, the next run can read.

The toggle is contribute_to_shared_pool. It is on by default. Set it to false and the run still reads the pool and writes nothing to it.

What this actor contributes. One contribution per run, covering what the three stages produced together: the creators found, the profiles read, the manager contacts, and the matched agencies. Not one contribution per stage.

Only public data that is already in your own output. Every field written to the pool is a field this run returned to you, read from a page the platform or the creator publishes to anyone without a login. Nothing from your Apify account, your input list, your API keys, or your own notes is sent. A contribution never deletes anything from the pool.

What a contribution is labeled with. The actor ID, the run ID, the pool key issued to the actor build, and a hash of the calling IP address, used for the rate limit and nothing else. Your Apify account and your user ID are not recorded.

Contributing is free. No event is charged for a write to the pool. If the pool is unreachable the run finishes as normal, the rows are dropped, and the run log says so.

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

Built by Mamba Labs.

Source: README.md at commit 9a858e6

Tools

1

build_influencer_lead_list

Build an Influencer Lead List End to End

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. Contributes the public records in its rows to a shared creator pool, free and on by default; `contribute_to_shared_pool` explains it and turns it off. A run that does not succeed is returned as an error with its run ID and status. Use it when you want discovery, profile, and link data in one call; when you only need one stage, the single stage tool is cheaper. Requires an APIFY_TOKEN and consumes Apify credits. Reads public data only and writes nothing.

Parametersmodenichehandlesus_onlyai_checkkeywordsplatformsai_api_keybatch_sizeskip_linksai_providerfollower_max+12 more

Version history

7
  1. v1.2.1LatestNov 5, 2026
  2. v1.2.0Oct 16, 2026
  3. v1.1.2Oct 12, 2026
  4. v1.1.1Oct 6, 2026
  5. v1.1.0Oct 6, 2026
  6. v1.0.1Sep 23, 2026
  7. v1.0.0Sep 22, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts