Server data from the Official MCP Registry
Resolve a company domain to Instagram, Threads and Facebook accounts and counts.
About
Resolve a company domain to Instagram, Threads and Facebook accounts and counts.
Security Report
This is a well-structured MCP server that properly authenticates with the Apify API using environment variables and makes read-only calls to the Apify actor platform. The code demonstrates good security practices with proper error handling, input validation via Zod, and no evidence of malicious patterns. The server's permissions are appropriate for its stated purpose of querying Meta social platform data through Apify. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
3 files analyzed · 6 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Environment variable: APIFY_TOKEN
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"com-mambabuilt-mcp-meta-brand-presence-mapper": {
"env": {
"APIFY_TOKEN": "your-apify-token-here"
},
"args": [
"-y",
"@mambalabsdev/mcp-meta-brand-presence-mapper"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
Instagram Threads Facebook Brand Presence Mapper MCP Server
MCP server for the Mamba Labs Instagram Threads 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:
{
"mcpServers": {
"mamba-meta-brand-presence-mapper": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-meta-brand-presence-mapper"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}
Prerequisites
- Node.js 18 or newer
- An Apify API token from console.apify.com/account/integrations
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
| Input | Type | Meaning |
|---|---|---|
company_domain | string | 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 |
company_name | string | Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches. |
handle | string | Optional. The Instagram handle with or without the leading @. Supplying it skips Instagram discovery AND gives Threads its handle for free, because Th |
platforms | array | Which 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 co |
includeFollowerCounts | boolean | When "true" (default) the profile page is fetched and the counts are extracted. Set "false" to resolve the profile URL only, which is cheaper and need |
skipCache | boolean | When "false" (default) a successful lookup is cached for seven days and reused. Set "true" to force a fresh fetch. Sent as a string for Clay compatibi |
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:
| Status | Meaning |
|---|---|
ok | fetched and parsed, the value is there |
not_found | we looked and there is no such profile |
not_extractable | the profile exists and the value is not on the wire to us |
blocked | the platform refused us, worth retrying later |
identity_mismatch | we found a real profile and it belongs to someone else |
skipped | you 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.
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
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.