Mcp Creator Profile Reader

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

Read influencer profiles by handle across seven platforms: followers, engagement, bio, and bio link.

Overview

AI-generated overview

Reads public influencer profiles by handle or URL across TikTok, Instagram, YouTube, Pinterest, Twitch, Threads and podcasts, returning one row per creator.

What you can do
  • Read creator profiles from handles or profile URLs on seven platforms
  • Return one flat row per creator with display name, follower and following counts, post count, engagement rate, verified flag, bio, bio link and public business email
  • Report unreadable creators as labeled error rows with a status and reason instead of omitting them
  • Optionally restrict results to US creators and cap run cost in USD
When to use it
Useful when you want an assistant to pull public creator metrics and bios for a known list of influencers, for example to compare engagement or assemble a shortlist. It reads specific creators only; it does not search for new ones.
Requirements
Runs locally via npx (Node.js) as a stdio process, desktop client only. Requires an Apify account and an APIFY_TOKEN environment variable. Optional Twitch client id and app token enable the official Twitch API. Network access to Apify and the platforms is needed.
Before you install
Usage is billed per event on Apify: a start fee, a per-profile read fee, and an extra Instagram bio fetch fee when residential proxy reads are used. By default the run contributes the public profile rows it returns to a shared creator and agency pool that other users read; set contribute_to_shared_pool to false to write nothing. Residential proxy escalation is on by default and can incur extra charges; max_residential_reads and max_charge_usd cap spending. Optional Twitch credentials are…

Installation

In SourceWeft

  1. Open Mcp Creator Profile Reader 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 Profile Scraper MCP Server

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

[Creator Profile Reader MCP server]

MCP server for the Mamba Labs Influencer Profile Scraper actor on Apify.

Creator handles or profile URLs in, one profile row out per creator.

Install

bash
npx -y @mambalabsdev/mcp-creator-profile-reader

Claude Desktop

json
{  "mcpServers": {    "mamba-creator-profile-reader": {      "command": "npx",      "args": ["-y", "@mambalabsdev/mcp-creator-profile-reader"],      "env": { "APIFY_TOKEN": "your-apify-token" }    }  }}

Get an Apify token at console.apify.com/account/integrations.

Tool

read_influencer_profiles

Read influencer profiles by handle across seven platforms: followers, engagement, bio, and bio link.

InputTypeRequiredNotes
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 a bare @handle is looked up on. A full profile URL carries its own platform and ignores this. This actor does not search; pass the creators you want read. Supported: TikTok, Instagram, YouTube,.
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.
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.
max_residential_readsintegernoCaps how many Instagram profile pages one run reads over the residential proxy (each readable one charges instagram-bio-fetch). 0 means no cap. Only acts when escalate_on_block is on. Default 0.
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.
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 Profile Scraper 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 Profile Scraper 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.001Once 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.
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.
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. The profile row for every creator it reads: platform, handle, display name, follower count, bio, bio link, public business email, engagement rate, verified flag, and the read date.

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 EqEnklDVMIcB1V499. 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 53a4753

Tools

1

read_influencer_profiles

Read Influencer Profiles by Handle

Reads creator profiles on TikTok, Instagram, YouTube, Pinterest, Twitch, Threads, and podcasts from handles or profile URLs. Returns one flat row per creator with display name, follower count, following count, post count, engagement rate, verified flag, bio text, bio link, any public business email, a country guess with the method behind it, and a stable creator_id. Engagement rate is lifetime likes per post over followers, and the method is named on the row rather than implied. It reads profiles only: it does not follow the bio link, which is what Link in Bio Scraper and Newsletter Detector does. Every row carries row_status and error_reason. Charges $0.001 per run plus $0.006 per profile read, and $0.01 per Instagram bio fetch when one is needed. 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 hold handles and need profile fields; to discover creators by keyword use Influencer Finder. Requires an APIFY_TOKEN and consumes Apify credits. Reads public data only and writes nothing.

Parametershandlesus_onlyplatformsbatch_sizemax_charge_usdtwitch_app_tokentwitch_client_idescalate_on_blockmax_residential_readscontribute_to_shared_pool

Version history

6
  1. v1.2.1LatestNov 5, 2026
  2. v1.2.0Oct 16, 2026
  3. v1.1.1Oct 6, 2026
  4. v1.1.0Oct 6, 2026
  5. v1.0.1Sep 23, 2026
  6. 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