Influencer Finder MCP Server
Related Servers
Alternatives to Influencer Finder MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceEnables AI-native creator discovery for influencer marketing, including creator search, lookalikes, profile lookup, and Instagram post transcript analysis.1426 npm1MIT- AlicenseAqualityAmaintenanceEnables reading influencer profiles by handle or profile URL across seven platforms, returning followers, engagement, bio, and bio link in a single row per creator.165 npmMIT
- AlicenseAqualityAmaintenanceEnables users to turn keywords or social media handles into finished influencer lead lists with contact details, using the Apify actor.189 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive influencer marketing data from Instagram, YouTube, and TikTok via the CreatorDB Headless API V3. It enables advanced creator search, profile analysis, and access to performance metrics and audience demographics.MIT
- AlicenseAqualityAmaintenanceEnables matching influencers to their talent agencies and agencies to their public creator rosters through an Apify actor.192 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables social media creators to pull TikTok, Instagram, Facebook, and YouTube analytics into a persistent vault, receive weekly digests, review scripts, build media kits, and draft brand outreach using official APIs only.MIT
TDQS
Scored across 1 tool
With only one tool exposed, there is no possibility of selecting the wrong tool or confusing overlapping purposes. The description's references to sibling servers (Profile Scraper, Link in Bio Scraper) are out of scope for this set and do not create internal ambiguity.
The single tool uses a clean verb_noun snake_case pattern (find_influencers) that directly reflects its action and resource. There are no competing conventions to clash with.
One tool for a whole server is thin even for a narrowly scoped discovery service; a user has no way to list niches, retrieve a run's results by ID, or look up a creator by the creator_id the tool returns. The single tool is rich, but the surface is borderline minimal.
The discovery step is well covered across many platforms and the tool honestly declares its boundary (no bios, emails, or link-in-bio), which are handled by separate servers. However, within this server there is no follow-up operation: no pagination, no fetch-by-run-id, no lookup by the advertised stable creator_id, and no way to act on the shared pool it contributes to.