mcp-pinterest-brand-presence-mapper
Related Servers
Alternatives to mcp-pinterest-brand-presence-mapper
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables resolving a company domain to its Instagram, Threads, and Facebook accounts with follower and post counts.190 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 any combination of company name, domain, or LinkedIn URL into the canonical company identity (name, domain, LinkedIn URL) with confidence scores and match method.166 npmMIT
- AlicenseAqualityAmaintenanceMaps a company domain to its official social media URLs and follower counts across LinkedIn, X, Instagram, Facebook, and YouTube.1108 npmMIT
- AlicenseNot gradedqualityCmaintenanceDomain -> company intelligence for AI agents. Look up company name, country, contacts, and social profiles from any MCP-compatible client.6MIT
TDQS
Scored across 1 tool
With only one tool in the set, there is no possibility of selecting the wrong tool or confusing overlapping purposes. The single tool has one clearly stated job: domain -> Pinterest business account enrichment row.
The lone name 'map_pinterest_brand_presence' follows a clean verb_noun snake_case convention that matches the server's stated purpose. There is no competing convention to create inconsistency.
One tool is thin even for a narrowly scoped enrichment server; there is no companion for batch input, board-level detail, or verification retries. It is borderline rather than wrong, since the single tool does perform the entire advertised mapping.
For its stated purpose the tool covers identity resolution, the four counts, claim/merchant verification, and an explicit identity_mismatch failure mode, which is solid lifecycle coverage. Gaps remain: no board- or pin-level drilldown, no historical/trend data, and no batch or multi-domain input.