Influencer Talent Agency Lookup MCP Server

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.

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.

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.

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