Mcp X Brand Presence Mapper

com.mambabuilt由 mambabuilt.com 发布v1.2.1更新于 Nov 5, 2026

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

已验证STDIO仅桌面网页搜索与抓取商业与电商

概览

AI 生成的概览

把公司域名或 X 账号解析为该公司的官方 X（Twitter）账号，返回账号名、主页链接、粉丝数据与简介，每家公司一行扁平记录。

可以做什么
  • 根据公司域名或 X 账号解析出官方 X 主页链接与账号名
  • 获取粉丝数、关注数、发帖数、认证状态、简介、显示名称与账号创建时间
  • 按行返回状态与抓取路径，区分未找到、无法提取与身份不匹配等结果
  • 每家公司返回一行扁平 snake_case JSON 字段，便于直接放入表格或 Clay 类工具
适用场景
适合需要为一批公司域名补充官方 X 账号与受众数据的场景，例如线索名单、品牌监测或 GTM 调研。它是单一用途的查询工具，并非通用的社交媒体客户端。
运行要求
通过 npx 在本地运行，需要 Node.js 18 或更高版本。需要 Apify 账号，并通过 APIFY_TOKEN 环境变量提供 Apify API 令牌；查询本身在 Apify 上执行。可选：每次调用可传入自己的 X API v2 bearer token，以便在大批量时获得完整指标。
安装前请注意
按事件计费，费用计入你的 Apify 账号，运行会消耗额度；可为单次调用设置费用上限。必须提供 APIFY_TOKEN 密钥，也可选传入 X API bearer token。查询数据会发送给 Apify 与 X 等第三方。未提供 X 令牌时，大批量查询可能返回计数为 not_extractable 的行。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Mcp X Brand Presence Mapper，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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

来源：README.md，提交 00bf9f1

工具

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.

输入参数handleskipCachecompany_namecompany_domainmax_charge_usdxApiBearerTokenincludeFollowerCounts

版本历史

5
  1. v1.2.1最新Nov 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

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分