Instagram Facebook Brand Presence Mapper

com.mambabuiltPublished by mambabuilt.comv1.2.2Updated Nov 7, 2026

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

VerifiedSTDIODesktop onlyWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Resolves a company domain to its Instagram, Threads and Facebook accounts with follower and post counts, as one flat row.

What you can do
  • Map a company domain or Instagram handle to its Instagram, Threads and Facebook profiles
  • Read follower and post counts, with per-platform status flags and Meta's own display strings
  • Derive the Threads handle from the resolved Instagram handle at no extra discovery cost
  • Optionally resolve profile URLs only, without fetching follower counts
  • Return one flat row keyed on company domain for spreadsheet or Clay-style enrichment
When to use it
Useful for GTM, sales or marketing research that needs a company's social footprint: checking whether a brand is on Threads, comparing follower counts, or finding a Facebook Page for a list of domains.
Requirements
Runs locally via npx, so Node.js 18 or newer is needed. Requires an Apify API token supplied in the APIFY_TOKEN environment variable; the lookup runs on the provider's Apify actor and is billed to that Apify account.
Before you install
Each call consumes Apify credits under pay-per-event pricing (actor start, company checked, platform resolved, follower count extracted), so costs accumulate per domain and platform; an optional max_charge_usd cap limits a single call. The APIFY_TOKEN is a secret and should not be shared. Facebook results are often blocked by a login wall, and null values mean unknown rather than absent.

Installation

In SourceWeft

  1. Open Instagram Facebook 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

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

Source: README.md at commit c3682f4

Tools

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.

ParametershandleplatformsskipCachecompany_namecompany_domainmax_charge_usdincludeFollowerCounts

Version history

6
  1. v1.2.2LatestNov 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

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