Instagram Facebook Brand Presence Mapper

com.mambabuilt由 mambabuilt.com 发布v1.2.2更新于 Nov 7, 2026

Resolve a company domain to Instagram, Threads and Facebook accounts and counts.

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

概览

AI 生成的概览

把公司域名解析为对应的 Instagram、Threads 和 Facebook 账号及粉丝数、帖子数，输出为一行扁平数据。

可以做什么
  • 将公司域名或 Instagram 用户名映射到其 Instagram、Threads 和 Facebook 主页
  • 读取粉丝数与帖子数，并附带各平台状态标记和 Meta 自带的显示字符串
  • 由解析出的 Instagram 用户名免费推导 Threads 用户名，不额外消耗发现成本
  • 可选择只解析主页链接而不抓取粉丝数
  • 返回以公司域名为键的一行扁平数据，便于表格或 Clay 类工具做数据补全
适用场景
适合 GTM、销售或市场调研场景：需要了解某公司的社交媒体布局、确认品牌是否已入驻 Threads、比较粉丝数，或为一批域名查找 Facebook 主页。
运行要求
通过 npx 在本地运行，需要 Node.js 18 或更高版本。需要在 APIFY_TOKEN 环境变量中提供 Apify API 令牌；查询由提供方的 Apify actor 执行，费用计入该 Apify 账户。
安装前请注意
每次调用都会消耗 Apify 额度，按事件计费（actor 启动、公司检查、平台解析、粉丝数提取），按域名和平台累加；可用 max_charge_usd 限制单次调用花费。APIFY_TOKEN 属于机密，不应外泄。Facebook 结果常因登录墙而失败，null 表示未知而非不存在。

安装

在 SourceWeft 中

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

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

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Instagram Facebook Brand Presence Mapper MCP Server

[Glama score] [npm version] [npm downloads] [license]

[Meta Brand Presence Mapper MCP server]

MCP server for the Mamba Labs Instagram Facebook Brand Presence Mapper actor on Apify.

Resolve a company domain to its Instagram, Threads and Facebook accounts with follower and post counts.

What it does

Resolve a company domain to its Instagram, Threads and Facebook accounts with follower and post counts, as one flat Clay ready row. The Threads handle is derived from the resolved Instagram handle at no extra discovery cost. Instagram and Threads counts are rounded by Meta and the row carries both the rounded integer and the platform's own display string. Facebook is best effort: Meta serves a login wall to anonymous clients, so blocked is a normal answer there and never a zero. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

Quick start

Add this to your MCP client configuration:

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

Prerequisites

The actor is pay per event and consumes Apify credits per call. Pricing is on the actor page.

Example prompts

  • "Get the Instagram and Threads follower counts for glossier.com."
  • "Has oatly.com adopted Threads yet, and how many posts do they have?"
  • "Find the Facebook Page for everlane.com."

Tool and inputs

Tool: map_meta_brand_presence

InputTypeMeaning
company_domainstringBare 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_namestringOptional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches.
handlestringOptional. The Instagram handle with or without the leading @. Supplying it skips Instagram discovery AND gives Threads its handle for free, because Threads handles are Instagram handles (5 of 5 measured).
platformsarrayWhich of the three Meta surfaces to map. Default is all three. Dropping Facebook is the common choice: it is the least reliable of the three and it costs a fetch to find that out.
includeFollowerCountsbooleanDefault true: the profile page is fetched and the follower counts are extracted. Set false to resolve the profile URL only, which is cheaper and needs no proxy.
skipCachebooleanDefault false: a successful lookup is cached for seven days and reused. Set true to force a fresh fetch.
max_charge_usdnumberOptional 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.

Reading the output

Every row carries a per platform _status field, and it is the field to read first. The vocabulary is the same across the whole Mamba Labs social family:

StatusMeaning
okfetched and parsed, the value is there
not_foundwe looked and there is no such profile
not_extractablethe profile exists and the value is not on the wire to us
blockedthe platform refused us, worth retrying later
identity_mismatchwe found a real profile and it belongs to someone else
skippedyou did not ask for this platform

false and null are never interchangeable. false means we looked and the answer is no. null means we could not look. If you filter for companies with no presence, filter on false, because null rows are unknown rather than absent.

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.005 on the Free plan, down to $0.0035 on higher Apify plansOnce per company for which the discovery cascade completed and a non degraded row was produced, whether or not any Meta platform resolved. Does not fire on a degraded row, because on a degraded row the company site was never read and no presence was measured.
platform-resolved$0.003 on the Free plan, down to $0.0021 on higher Apify plansOnce per REQUESTED Meta platform whose candidate URL passed the identity gate. Fires on the validation work, not on a populated follower cell. A candidate dropped as an impersonator does not charge: the work was done and the answer is that there is no such profile. A platform the caller did not request never fires it.
follower-count-extracted$0.0025 on the Free plan, down to $0.00175 on higher Apify plansOnce per Meta platform where a numeric follower count was read off the public Open Graph card. Does not fire on not_extractable, blocked, identity_mismatch or a URL only run. Facebook therefore often does not fire it, which is correct: it is the platform we most often cannot read.

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

Full actor documentation

apify.com/mambalabs/meta-brand-presence-mapper

Mamba Labs GTM Suite

Mamba Labs builds a fleet of GTM enrichment actors that share one flat, Clay ready output convention, so their rows join on company_domain with no cleaning step. Full fleet: apify.com/mambalabs

License

MIT

来源：README.md，提交 c3682f4

工具

1

map_meta_brand_presence

Map Instagram Threads and Facebook Presence

Resolve a company domain to its Instagram, Threads and Facebook accounts with follower and post counts, as one flat Clay ready row. The Threads handle is derived from the resolved Instagram handle at no extra discovery cost. Instagram and Threads counts are rounded by Meta and the row carries both the rounded integer and the platform's own display string. Facebook is best effort: Meta serves a login wall to anonymous clients, so blocked is a normal answer there and never a zero. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

输入参数handleplatformsskipCachecompany_namecompany_domainmax_charge_usdincludeFollowerCounts

版本历史

6
  1. v1.2.2最新Nov 5, 2026
  2. v1.2.1Oct 16, 2026
  3. v1.2.0Oct 16, 2026
  4. v1.1.1Oct 6, 2026
  5. v1.1.0Oct 6, 2026
  6. v1.0.0Sep 16, 2026

评分

已满足适用检查项的 90%

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

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

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

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