mcp-meta-brand-presence-mapper
Related Servers
Alternatives to mcp-meta-brand-presence-mapper
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMaps a company domain to its official social media URLs and follower counts across LinkedIn, X, Instagram, Facebook, and YouTube.1108 npmMIT
- AlicenseAqualityAmaintenanceResolves TikTok handles or company domains to brand accounts, returning follower, like, video counts, verification status, and more.188 npmMIT
- AlicenseAqualityAmaintenanceResolves company domains to their LinkedIn pages, providing exact follower counts and public firmographics such as industry, company size band, headquarters, founded year, and specialties.198 npmMIT
- AlicenseAqualityAmaintenanceResolves a company domain to its Pinterest business account, returning exact follower, following, pin, and board counts along with claimed website, verified merchant status, and per-platform status indicators for identity mismatches and other outcomes.180 npmMIT
- AlicenseNot gradedqualityCmaintenanceDomain -> company intelligence for AI agents. Look up company name, country, contacts, and social profiles from any MCP-compatible client.6MIT
- AlicenseAqualityBmaintenanceEnables users to look up a person's public GitHub, Bluesky, personal site, Substack, and X profiles from their full name and company domain, with status and confidence per platform and no emails or phone numbers.10MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlap. Its purpose (domain → Meta account resolution) is unambiguous from the name and description.
The single tool follows a clean verb_noun snake_case pattern (map_meta_brand_presence) that clearly states the action and resource. With one tool there is no convention mixing to penalize.
A single tool is thin even for a narrow enrichment server, sitting below the typical 3-15 range. The scope (one read-only resolution call) plausibly justifies it, but there is no separate tool for batched input or per-platform retries.
The tool covers the stated domain end to end: domain resolution into Instagram, Threads, and Facebook with counts, and it honestly documents Facebook's best-effort limitation. Minor gaps exist—no bulk/multi-domain input, no retry or credential-check companion tool—but core coverage is solid.