Which integrations are available for this server?

Supports influencer talent agency lookup using Apple Podcasts show pages, matching a podcast creator to their talent agency or an agency to its public roster. Supports influencer talent agency lookup using Instagram profile handles, matching creators to their talent agency or listing an agency's Instagram creators from its public roster. Supports influencer talent agency lookup using Pinterest profiles, matching creators to their talent agency or listing an agency's Pinterest creators from its public roster. Supports influencer talent agency lookup using Spotify show pages, matching podcast creators to their talent agency or an agency to its public roster. Supports influencer talent agency lookup using Threads profiles, matching creators to their talent agency or listing an agency's Threads creators from its public roster. Supports influencer talent agency lookup using TikTok profile handles, matching creators to their talent agency or listing an agency's TikTok creators from its public roster. Supports influencer talent agency lookup using Twitch profiles, matching creators to their talent agency or listing an agency's Twitch creators from its public roster. Supports influencer talent agency lookup using YouTube channel handles, matching creators to their talent agency or listing an agency's YouTube creators from its public roster.

How do I use Influencer Talent Agency Lookup MCP Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Influencer Talent Agency Lookup MCP Server What agency represents tiktok:@mrbeast?" 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 Talent Agency Lookup MCP Server

by mambalabsdev

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Influencer Talent Agency Lookup MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

MCP server for the Mamba Labs Influencer Talent Agency Lookup actor on Apify.

Creator handles in, the talent agency behind each one out. Or an agency in, its public creator roster out.

Install

npx -y @mambalabsdev/mcp-talent-agency-lookup

Claude Desktop

{
  "mcpServers": {
    "mamba-talent-agency-lookup": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-talent-agency-lookup"],
      "env": { "APIFY_TOKEN": "your-apify-token" }
    }
  }
}

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

Related MCP server: Company Discovery List Builder MCP Server

Tool

`lookup_influencer_talent_agency`

Match an influencer to their talent agency, or an agency to its public creator roster.

Pass handles for creator to agency, or agency_domains or agency_names for agency to roster. Both directions can run in one call.

Input	Type	Required	Notes
`handles`	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 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.
`platforms`	array	no	Which 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, Pinterest, Twitch, Threads, and podcasts. Not X, not Facebook pages, not LinkedIn.
`agency_domains`	array	no	Agency to roster: one domain per line (for example viralnation.com). Returns one row per creator on the agency's public roster.
`agency_names`	array	no	Agency to roster by name when you do not have the domain. Exact or partial name match against the list.
`render_unreadable_pages`	boolean	no	Off by default. Some agency roster pages build their talent grid in the browser and return an empty shell to a plain fetch, so the roster reads as empty. Turn this on to render those pages in a headless browser and read the roster from the rendered page. Charged per page rendered (event browser-render) to cover the browser compute, and only when the rendered page comes back readable. A page that answers with a bot challenge is recorded as blocked and is never rendered. Default `false`.
`escalate_on_block`	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 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`.
`batch_size`	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.
`contribute_to_shared_pool`	boolean	no	On by default. The run contributes the public records it finds to a shared creator and agency pool that all users of this actor read from, so a later run reads what this one found. Only public data that is already in your own output rows is sent: nothing from your Apify account, your input list, your API keys, or your own notes. Nothing is charged for a contribution. Turn this off and the run still reads the pool and writes nothing to it. Default: true.

Nothing is required, but a call with no handles, no agency_domains, and no agency_names has nothing to look up and the run fails with a message saying so.

Pricing

Influencer Talent Agency Lookup is pay per event on Apify. Every price below is flat across the FREE, BRONZE, SILVER, GOLD, PLATINUM, and DIAMOND tiers.

Event	Charged for	Price	Fires when
`actor-start`	Actor start	$0.001	Once per run, on start. Covers the run overhead.
`agency-lookup`	Agency lookup	$0.008	Once per row returned by the talent agency lookup, in either direction (creator to agency, or agency to a roster creator).
`browser-render`	Browser render	$0.004	Once per agency roster page rendered in the headless browser because the plain fetch returned an empty shell, and only when the rendered page came back readable. Only when `render_unreadable_pages` is on.
`instagram-bio-fetch`	Instagram bio fetch	$0.01	Once per Instagram profile row when the bio, bio link, and following were read from the profile page over the residential proxy and came back readable. Only when `escalate_on_block` is on.

Reading the output

Every row carries agency_match_method: email_domain_exact, email_domain_parent, public_roster, bio_wording, or no_match. A no_match row names the email domains it tried in error_reason. Every row also carries row_status and error_reason, so a creator or an agency the actor could not read comes back as a row saying why, not as a gap in the list. Filter on row_status before loading a table.

Coverage is partial by construction. The bundled list holds 143 agencies and 557 roster creators, seeded from 13 public directories, and it grows through the shared pool.

What this actor shares

This 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.

This actor reads the pool before it reads anything else. When the pool is unreachable it falls back to the agency list bundled in the build, so a run never fails on the pool.

The toggle is contribute_to_shared_pool. It is a boolean input and it is on by default. Turn it off and the run still reads the pool and writes nothing to it.

What this actor contributes. The agency rows and the roster rows read during the run: agency name, domain, public contact, country, classification, roster URL, and one roster row per creator with the platform and the handle.

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 zCuX4Mgyg6JvXgGzd. 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
Influencer Finder	`tpkedmloIIWtXx6sg`	`@mambalabsdev/mcp-creator-finder`
Influencer Profile Scraper	`EqEnklDVMIcB1V499`	`@mambalabsdev/mcp-creator-profile-reader`
Link in Bio Scraper and Newsletter Detector	`OorucdheTIgu7RFzK`	`@mambalabsdev/mcp-link-in-bio-newsletter-checker`
Influencer Change Monitor	`d2VVgahNL6UmcLkhg`	`@mambalabsdev/mcp-creator-change-monitor`
Influencer Lead List Builder	`KnmByszcv135yM30G`	`@mambalabsdev/mcp-creator-lead-list-all-in-one`
Influencer Talent Agency Lookup	`zCuX4Mgyg6JvXgGzd`	`@mambalabsdev/mcp-talent-agency-lookup`

Built by Mamba Labs.

Available Tools

1 tool

lookup_influencer_talent_agencyLook Up an Influencer's Talent Agency or an Agency's RosterA

Read-onlyIdempotent

Works in two directions. Creator to agency: pass creator handles or profile URLs and get one row per creator with the talent agency that represents them, its domain, its public contact, and agency_match_method (email_domain_exact, email_domain_parent, public_roster, bio_wording, or no_match with the email domains tried in error_reason). Agency to roster: pass agency domains or agency names and get one row per creator on the agency's public roster, with platform, handle, and profile URL. The agency list is seeded from 13 public directories and holds 143 agencies and 557 roster creators; coverage is partial and every row says how it matched. Supports TikTok, Instagram, YouTube, Pinterest, Twitch, Threads, and podcasts. Charges $0.001 per run plus $0.008 per row returned, $0.004 per agency roster page rendered in the headless browser when render_unreadable_pages is on and the rendered page comes back readable, and $0.01 per Instagram bio fetch when one is needed. Contributes the public records it finds to a shared creator and agency pool that all users of this actor read from, so a later run reads what this one found; contribute_to_shared_pool is on by default and turning it off leaves the run reading the pool and writing nothing. Only public data already in the returned rows is contributed, nothing from your Apify account or your input, and a contribution is not charged. Requires an APIFY_TOKEN and consumes Apify credits. Read only.

ParametersJSON Schema

Name	Required	Description
`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.
`platforms`	No	Which 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, Pinterest, Twitch, Threads, and podcasts. Not X, not Facebook pages, not LinkedIn.
`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.
`agency_names`	No	Agency to roster by name when you do not have the domain. Exact or partial name match against the list.
`agency_domains`	No	Agency to roster: one domain per line (for example viralnation.com). Returns one row per creator on the agency's public roster.
`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.
`render_unreadable_pages`	No	Off by default. Some agency roster pages build their talent grid in the browser and return an empty shell to a plain fetch, so the roster reads as empty. Turn this on to render those pages in a headless browser and read the roster from the rendered page. Charged per page rendered (event browser-render) to cover the browser compute, and only when the rendered page comes back readable. A page that answers with a bot challenge is recorded as blocked and is never rendered.
`contribute_to_shared_pool`	No	On by default. The run contributes the public records it finds to a shared creator and agency pool that all users of this actor read from, so a later run reads what this one found. Only public data that is already in your own output rows is sent: nothing from your Apify account, your input list, your API keys, or your own notes. Nothing is charged for a contribution. Turn this off and the run still reads the pool and writes nothing to it. Default: true.

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds substantial behavioral context: cost per run and per row, shared pool contribution behavior, retry on bot detection, and rendering of unreadable pages. It also clarifies that contributions only include public data already in output, and that turning off the pool still reads it. No contradiction with annotations.

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 quite long but justified given the tool's complexity: two modes, multiple parameters, cost structure, shared pool behavior, and edge cases. It is front-loaded with the core purpose ('Works in two directions') and then systematically details each aspect. While verbose, every sentence adds value; it avoids redundancy.

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?

The description covers all necessary aspects: input formats, output row contents for both modes, cost breakdown, shared pool semantics, handling of bot detection, and parameter defaults. Since there is no output schema, the description explicitly describes the returned rows for each direction, making it complete for an agent to call correctly.

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?

Schema coverage is 100%, so all parameters have detailed descriptions. The tool description adds context on how parameters interplay (e.g., the two modes, batch size measurement, escalate_on_block behavior) but does not fundamentally add meaning beyond what the schema already provides. The baseline for high schema coverage is 3, and the description does not significantly elevate it.

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 clearly states the tool's dual purpose: mapping creators to agencies and agencies to rosters. It uses specific verbs ('look up', 'get') and resources ('talent agency', 'roster'), and distinguishes the two directions explicitly. Although there are no sibling tools, the description is unambiguous about what the tool does.

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 explains exactly how to use each direction: passing creator handles for creator-to-agency, and agency domains/names for agency-to-roster. It also provides context like 'This actor does not search; pass the creators you want read' and lists unsupported platforms. However, it does not explicitly compare to alternatives (there are none) or provide conditional 'when to use' guidance beyond the two modes.

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 updatev1.0.1Sep 23, 2026
- First observedlookup_influencer_talent_agency

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored 2026-09-23 11:30 across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusing it with another. The single tool clearly bundles two lookup directions under one descriptive name.

Naming Consistency5/5

The lone tool name follows a clear verb_noun pattern: 'lookup_influencer_talent_agency'. There are no other names to conflict or mix conventions with.

Tool Count2/5

One tool for a fairly broad domain (creator-to-agency, agency-to-roster, multi-platform coverage) feels thin. While the tool is not trivial, the server would benefit from separating these into distinct tools, e.g. lookup_agency_for_creator and list_roster_for_agency.

Completeness4/5

The tool covers both primary lookup directions and returns match metadata, so agents can accomplish the core task. Minor gaps exist such as no explicit pagination or filtering options beyond the single call, but these are workable within the results.

Maintenance

ActivityNo data

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

mcp A
com.getcims
Manage 230M+ influencers, track campaigns, and access real-time CIMS analytics via AI agents
Social Media Marketing Monitoring
2
CreatorDBOAuth
app.creatordb
Creator discovery & analytics across YouTube, Instagram, TikTok (30M+) + brand/sponsor intel.
Social Media Marketing
12
Influship A
io.github.Influship
Find and analyze influencers with creator search, lookalikes, profiles, posts, and transcripts.
Social Media Marketing
3721
Viral Manager A
com.viral-managers
Virality detection for creator agencies: find viral posts, AI breakdowns, creator briefs.
Social Media
611

Related MCP Servers

Influship MCPofficial
Marketing Social Media Search
Influship
A
license
A
quality
C
maintenance
Enables AI-native creator discovery for influencer marketing, including creator search, lookalikes, profile lookup, and Instagram post transcript analysis.
Updated 4 months ago (2026-06-06 14:31 UTC)
14
35 npm
1
MIT
Company Discovery List Builder
Web Scraping Research & Data
mambalabsdev
A
license
A
quality
A
maintenance
Enables building targeted company lists from live job boards or SEC filings via the Apify actor, supporting role keywords, locations, and filing phrases.
Updated 9 days ago (2026-09-14 04:35 UTC)
1
37 npm
MIT
genpark-creator-audienceofficial
Marketing Social Media Research & Data
alphaparkinc
F
license
Not graded
quality
B
maintenance
Enables AI agents and MCP clients to identify creator audience lookalike clusters and measure affinity overlap, producing structured output dossiers with deterministic zero-dependency execution.
Updated 21 days ago (2026-09-02 10:22 UTC)
8
-
genpark-ugc-creator-briefofficial
Autonomous Agents Marketing
alphaparkinc
F
license
Not graded
quality
B
maintenance
Enables autonomous matching of UGC creators to brand briefs via a deterministic programmatic auction and video matchmaking workflow. It integrates as an MCP server so AI agents can run creator brief auctions and produce structured results with execution telemetry.
Updated 21 days ago (2026-09-02 10:27 UTC)
9
-

Influencer Talent Agency Lookup MCP Server

Install

Claude Desktop

Tool

lookup_influencer_talent_agency

Pricing

Reading the output

What this actor shares

Actor

Suite

Available Tools

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Influship MCPofficial

Company Discovery List Builder

genpark-creator-audienceofficial

genpark-ugc-creator-briefofficial

`lookup_influencer_talent_agency`