Mcp X Brand Presence Mapper

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

Resolve a company domain to its X handle, profile URL and follower metrics.

VerifiedSTDIODesktop onlyWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Resolves a company domain or X handle to the company's official X (Twitter) profile, returning handle, URL, follower metrics and bio as one flat row.

What you can do
  • Resolve a company domain or X handle to an official X profile URL and handle
  • Retrieve follower, following and post counts, verification status, bio, display name and account creation date
  • Report per-row status and fetch route, distinguishing not found, not extractable and identity mismatch results
  • Return one flat snake_case JSON row per company, ready for spreadsheet or Clay-style tables
When to use it
Useful when you need to enrich a list of company domains with their official X accounts and audience metrics, for example for lead lists, brand monitoring or GTM research. It is a single-purpose lookup tool rather than a general social media client.
Requirements
Runs locally via npx, so Node.js 18 or newer is needed. An Apify account and an Apify API token supplied in the APIFY_TOKEN environment variable are required; the lookup itself runs on Apify. Optionally, your own X API v2 bearer token can be passed per call for full metrics on large batches.
Before you install
Usage is billed per event to your Apify account, so runs consume credits; a per-call spending cap can be set. The APIFY_TOKEN secret is required, and an optional X API bearer token may be passed. Lookups are sent to Apify and X as third parties. Without an X token, large batches may return rows with counts marked not_extractable.

Installation

In SourceWeft

  1. Open Mcp X Brand Presence Mapper 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

X Twitter Brand Presence Mapper MCP Server

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

[X Brand Presence Mapper MCP server]

An MCP server that resolves a company domain to its X (Twitter) handle, profile URL and follower metrics. It wraps the Mamba Labs X Twitter Brand Presence Mapper actor on Apify and returns a Clay-ready flat JSON row to any MCP client.

What's Inside

What it does

Give it a company domain and it returns that company's official X handle and profile URL, with the follower, following and post counts, verification status, bio and account creation date where X serves them. One flat row per company.

It runs keyless out of the box. X rate limits the public route aggressively, so on a large batch some rows come back with the handle and URL populated and the counts marked not_extractable. Supplying your own X API bearer token removes that limit and returns full metrics at any batch size. The key raises effectiveness rather than unlocking the tool.

A guessed handle that fails the identity check is reported as identity_mismatch rather than returned as the company's. All of the lookup runs on Apify. This package is a thin client that calls the actor and hands back the result unchanged.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config:

json
{  "mcpServers": {    "mamba-x-brand-presence-mapper": {      "command": "npx",      "args": ["-y", "@mambalabsdev/mcp-x-brand-presence-mapper"],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The map_x_brand_presence tool will be available.

Prerequisites

  • Node.js 18 or newer
  • An Apify account with an API token
  • Optional: your own X API v2 bearer token, free to create at developer.x.com, if you want full metrics on a large batch

Example prompts

  • "Find the X account for shopify.com and give me its follower count."
  • "What is the X handle for stripe.com, and when was the account created?"
  • "Resolve the X profile URL for figma.com without fetching follower counts."
  • "Look up the X handle Shopify and return the bio and post count."

Inputs

  • company_domain (optional): bare company domain, for example shopify.com. Supply this or a handle. With a domain the actor runs full discovery; with a handle it skips straight to the fetch.
  • company_name (optional): improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches.
  • handle (optional): the X handle with or without the leading @, for example Shopify. Supplying it skips discovery and goes straight to the fetch.
  • includeFollowerCounts (optional): when true (the default) the profile page is fetched and the counts are extracted. Set false to resolve the profile URL only, which is cheaper and needs no proxy.
  • skipCache (optional): when false (the default) a successful lookup is cached for seven days and reused. Set true to force a fresh fetch.
  • xApiBearerToken (optional): your own X API v2 bearer token, free to create at developer.x.com. Without one the tool still resolves handles, profile URLs and follower counts, but X rate limits the public route so some rows in a large batch return not_extractable instead of counts. Your token is used for your run only, is never stored, and is never shared with another run.
  • max_charge_usd (optional): spending cap for this call, in USD. The actor stops before any charge that would take the run past this amount and keeps every row already charged.

Supply either company_domain or handle.

Output

The tool returns the actor's flat JSON row for the company, with 18 snake_case fields and no nested objects. Read x_status first: ok, not_found, not_extractable and identity_mismatch are different answers and the wrapper never collapses them. x_fetch_route says which route produced the counts and x_discovery says how the handle was found. See the Apify Store page for the full output schema.

Example output

json
{  "degraded": false,  "degradation_reason": null,  "company_domain": "shopify.com",  "company_name": "Shopify",  "x_url": "https://x.com/Shopify",  "x_handle": "Shopify",  "x_followers": 452243,  "x_followers_exact": true,  "x_following": 3423,  "x_tweet_count": 37167,  "x_verified": false,  "x_display_name": "Shopify",  "x_bio": "The entrepreneurship company",  "x_created_at": "2008-11-03T18:33:14.000Z",  "x_fetch_route": "syndication",  "x_discovery": "homepage_sameas",  "x_status": "ok",  "run_date": "2026-08-22T19:23:45.055Z"}

Features

  • Resolves an official X handle and profile URL starting from a company domain
  • Follower, following and post counts, plus verification status
  • Account creation date, bio and display name
  • Runs keyless, with your own X API key available for scale
  • Domain first discovery from the homepage sameAs markup
  • The fetch route is reported per row in x_fetch_route
  • 18 flat snake_case fields, one row per company

Pricing

You pay per event on Apify, billed to your own Apify account. Prices from the live pricing record, read 2026-10-16:

EventPrice per event (USD)Fires when
apify-actor-start$0.00005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
company-checked$0.0035 on the Free plan, down to $0.00245 on higher Apify plansOnce per company for which the discovery cascade completed and a non degraded row was produced, whether or not an X account was found. Does not fire on a degraded row, because on a degraded row no discovery was performed.
profile-resolved$0.003 on the Free plan, down to $0.0021 on higher Apify plansOnce per company whose candidate X URL passed the identity gate. Fires on the validation work, not on a populated count. This is the event that carries the actor in keyless mode, because handle resolution succeeds whether or not X served a count.
follower-count-extracted$0.0025 on the Free plan, down to $0.00175 on higher Apify plansOnce per company where a numeric follower count was actually read, from either route. A rate limited row does not fire it and is not charged for the count, which is deliberate: an event firing on a not_extractable row would be charging for the string not_extractable.

The actor's Apify page carries the current prices. Running this server consumes Apify credits.

Full actor documentation

This server is a thin client and holds no lookup logic. For the complete input and output reference, pricing, and run history, see the Apify Store page:

https://apify.com/mambalabs/x-brand-presence-mapper

Mamba Labs GTM Suite

This server is one of the Mamba Labs GTM Suite MCP servers. Every actor in the suite takes a domain or a company and returns one flat row, so they stack in the same Clay table without reshaping anything. The actor behind this server is the X Twitter Brand Presence Mapper, immutable Apify actor ID oLOgadhHUkNAyDA3w.

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

Source: README.md at commit 00bf9f1

Tools

1

map_x_brand_presence

Map X Twitter Brand Presence

Resolve a company domain to that company's official X (Twitter) handle and profile URL, with follower count, bio and account age where X serves them. Returns one flat Clay ready row. Runs keyless out of the box and X rate limits that route aggressively, so on a large batch some rows return the handle and URL with the counts marked not_extractable; supplying your own X API bearer token removes that limit and returns full metrics at any batch size. A guessed handle that fails the identity check is reported as identity_mismatch rather than returned as the company's, and a company with no X account reports x_status not_found. Read x_status before any count. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

ParametershandleskipCachecompany_namecompany_domainmax_charge_usdxApiBearerTokenincludeFollowerCounts

Version history

5
  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.0Sep 16, 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