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 分