If you're an AI reading this: skill.md has everything you need.Read it →
Explorer/MCP/influship/influship-mcp
REMOTE

Influship Influencer Marketing MCP

influship/influship-mcp

# Influship MCP Influship MCP gives AI agents access to influencer marketing and creator discovery workflows. Use it to search creators by niche, audience, location, platform, and campaign fit; find lookalike creators from known winners or competitor lists; resolve creator profiles and social handles; and pull creator records, posts, and Instagram transcript data into briefs, prospecting lists, market maps, and outreach research. ## What it can do - Search for creators across influencer marketing niches and campaign-fit criteria - Find lookalike creators from known creators, competitors, or talent lists - Resolve creator profiles and social handles - Retrieve creator records, recent posts, and profile details - Analyze Instagram post and transcript data for research and planning ## Authentication Smithery users should provide an Influship API key. The key is forwarded to the hosted MCP server as: ```text X-API-Key: <your_api_key>

14 tools available
The Journeyman
A reasonable amount of history and nothing concerning in the scan.
Time indexed (4mo)
14toolsRemote/ HTTP4moindexed
100% uptime · 318ms avgChecked Sep 14, 2026
Quality Score
43/95
Established
Risk Score
0/100
Clean
How is this calculated?
Quality Breakdown
Tenure12.9/20
111 days indexed
Capability18/25
Tools: 6/13 (14 tools)
Description: 5/5
Endpoint: 7/7
Adoption2.4/25
Use count: 2.4/20 (3 uses)
Multi-registry: 0/5 (1 registry)
Reliability10/25
Currently live: 10/10
Uptime history: 0/15 No checks yet
Security scan: 0 pts in v1.0; ready to weight when coverage improves
Risk
0Clean
No signals detected.
The scanner shows
14 tools. Nothing caught our attention.
First indexed May 28, 2026
Server Profile
Tools catalogued
14
14 tools available. Full list below.
Hosting
Remote / HTTP
Runs on the internet. No access to your filesystem, SSH keys, or environment variables.
Registry presence
Not verified
Not yet verified by the Official MCP Registry.
Liveness
100%
Based on 16 checks. Average response: 318ms.
Publisher Verification
Not yet verified by the Official MCP Registry.
Endpoint
https://influship.run.tools
Tools (14)
get_sample_creator
Use this when a ChatGPT user wants to see what Influship can return before linking an account. Fetches one configured sample creator with social profile context. This is a low-cost preview tool and should not be used for search, discovery, matching, or lookalike requests. After showing the preview, tell the user that real live creator data, search, lookalikes, matching, posts, and transcripts require connecting an Influship account. Explain that they can authorize either an Influship SaaS subscription, where usage counts against monthly bundled credits, or an Influship API account, where usage is billed pay-as-you-go under API billing.
search_creators
Find a creator by name/handle, while preserving legacy semantic creator search. Use this as the default creator lookup tool when the user gives a creator-ish string but not a canonical creator UUID: a handle, partial handle, display name, creator name, or profile-ish text. This is cheap, fast, and backed by the creator lookup index. If the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram"), prefer `get_profile` first because it returns the full platform profile. If you need to resolve a rough creator name or partial handle first, use this tool with `query_type: "creator_lookup"`. For backward compatibility, this tool still accepts the old semantic-search fields (`platforms`, follower/engagement filters, `creator_kinds`) and routes legacy calls to the semantic endpoint unless the query clearly contains a handle/profile URL. For new topical/niche discovery calls such as "fitness creators in NYC" or "vegan recipe creators with high engagement", prefer `semantic_search_creators` because its name is explicit and less likely to be confused with exact creator lookup. Examples: - User: "Find @cris" -> use this tool with query "cris" and query_type "creator_lookup". - User: "Who is that fitness coach called Jane?" -> use this tool with query "Jane" and query_type "creator_lookup". - User: "Pull @niickjackson on Instagram" -> use `get_profile` with platform "instagram" and username "niickjackson". - User: "Find news creators with 1M+ followers" -> use `semantic_search_creators`, not this tool. Returns either autocomplete-style creator lookup results or legacy semantic results, depending on routing. Use returned creator IDs with `get_creator`, `find_lookalike_creators`, or `match_creators`; use returned platform usernames with `get_profile` or `get_posts`.
semantic_search_creators
Semantic discovery search for influencers/content creators using natural-language queries. Use this only when the user asks to discover creators by topic, audience, geography, niche, content style, or campaign criteria (e.g., "fitness creators in NYC", "vegan recipe creators with high engagement", "tech reviewers who cover phones"). The query is matched against creator profiles, extracted facts, and visual style via hybrid vector search. Do not use this for exact handles, usernames, or known creator names. If the user gives a specific platform and handle (for example "@niickjackson on Instagram"), use `get_profile` first. For rough name/handle lookup, use `search_creators`. For multiple known handles, use `lookup_profiles`. Semantic search can return lookalike or topical matches and is allowed to miss an exact username. Examples: - User: "Find news creators with 1M+ followers" -> use this tool. - User: "Find creators in LA who make cinematic travel videos" -> use this tool. - User: "Pull @niickjackson on Instagram" -> use `get_profile`, not this tool. - User: "Is @niickjackson a fit for Pixel?" -> use `get_profile` first, optionally `get_posts`, then `match_creators`. Returns a ranked list of creators (id, platform, username, follower count, engagement rate, top categories, evidence facts). Use the flat follower, engagement-rate, and verified fields to constrain results when the user gives concrete numeric constraints. Use `find_lookalike_creators` instead when you want creators SIMILAR to known ones. Use `match_creators` when you want to SCORE specific creators against a brief.
autocomplete_creators
Autocomplete creator names, usernames, or display names from partial input. Use this for fast lookup when the user types a partial handle or name and you need to resolve it to canonical creator IDs (e.g., "find @cris" or "who's that fitness coach called Jane?"). Cheap and fast — prefer over `search_creators` for handle-style queries where the user already knows roughly who they want. Use `get_profile` instead when the user gives an exact platform+username pair. Use `search_creators` for the same fuzzy creator lookup behavior with a less typeahead- specific name. Use `semantic_search_creators` only for discovery by topic, niche, audience, geography, or content style, not for resolving a known creator. Examples: - User: "Who is that fitness coach called Jane?" -> use this tool. - User: "Find @cris..." -> use this tool to resolve the partial handle. - User: "Pull @niickjackson on Instagram" -> use `get_profile`, not this tool. Returns a short list of matching creators with their IDs, platforms, and display names. Use the IDs returned here as input to `get_creator`, `find_lookalike_creators`, or `match_creators` for downstream operations.
find_lookalike_creators
Find creators SIMILAR to one or more seed creators. Use this when the user already knows a creator they like and wants more like them (e.g., "find creators like @therock", "find more creators like these three I just booked"). Seeds are blended via creator-profile + visual-style + fact embeddings to surface similar accounts. Seeds are passed in `seed_creator_ids` (canonical UUIDs) and/or `seed_profiles` (platform + username; resolve handles via `autocomplete_creators` first if needed). Returns a ranked list of similar creators with scores. `limit` caps results (default 25, max 100). Use the flat follower, engagement-rate, and verified fields to constrain results. Use `semantic_search_creators` instead when you have a topic/niche but no seed. Use `match_creators` when you have specific candidates and want to score their fit against a brief. Examples: - User: "Find creators like @niickjackson on Instagram" -> use this tool with `seed_profiles: [{ platform: "instagram", username: "niickjackson" }]`. - User: "Find news creators with 1M+ followers" -> use `semantic_search_creators`, not this tool.
match_creators
Score how well specific creators fit a campaign brief or search intent. Use this when the user already has candidate creators in mind and wants to evaluate fit (e.g., "rate these 5 creators for a vegan cookbook launch", "which of these is the best match for my crypto audience?"). For each creator the API returns a match score (0-1), a good/neutral/avoid decision, and structured reasons. Pass candidates in `creator_ids` (canonical UUIDs) and/or `profiles` (platform + username). `intent_query` is the brief the LLM reasons against; `intent_context` is optional extra context (target audience, brand values, prior collabs). Use `semantic_search_creators` when you don't have candidates yet and need topical or niche discovery. Use `search_creators` first when you only need to resolve rough creator names/handles into candidates. Use `find_lookalike_creators` when you want creators similar to known good fits. Examples: - User: "Is @niickjackson a fit for Pixel?" -> use this tool after resolving the exact Instagram profile with `get_profile`; call `get_posts` first if recent content context is needed. - User: "Rate these five creators for a vegan cookbook launch" -> use this tool.
Show all 14 tools ↓
get_creator
Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.
get_profile
Fetch a single social profile by (platform, username). Always use this first when the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram") and you need the full profile: bio, follower/engagement metrics, recent activity, growth, and the canonical creator ID. Pass exactly the username they typed without the @ sign — case-insensitive matching is handled server-side. Do not use `search_creators` for an exact platform+username lookup. Examples: - User: "Pull @niickjackson on Instagram" -> use this tool with platform "instagram" and username "niickjackson". - User: "Tell me about instagram.com/niickjackson" -> parse the platform and username, then use this tool. - User: "Is @niickjackson a fit for Pixel?" -> use this tool first, then call `get_posts` and/or `match_creators` if the task needs content or fit analysis. Returns the profile record plus the underlying creator record. If you already have a creator UUID, use `get_creator` instead. For batch lookups by handle, use `lookup_profiles`.
lookup_profiles
Batch-fetch up to 100 profiles by (platform, username) pairs. Use this when the user has a list of handles and you need profile data for all of them at once (e.g., "give me follower counts for these 30 accounts I'm considering" or "which of @a @b @c are real accounts?"). One round-trip beats 30 calls to `get_profile`. Use this for exact batch handle lookup, not semantic discovery. For one exact platform+username pair, use `get_profile`. For partial or fuzzy handle/name input, use `search_creators` or `autocomplete_creators`. Use `semantic_search_creators` only for topical/niche/audience discovery where false-positive semantic matches are acceptable. Examples: - User: "Compare @a, @b, and @c on Instagram" -> use this tool for the exact handle batch. - User: "Give me follower counts for these 30 accounts" -> use this tool. - User: "Find wellness creators in Austin" -> use `semantic_search_creators`, not this tool. The response splits results into `data` (profiles found) and `not_found` (the (platform, username) pairs that weren't recognized). Profiles are returned in no particular order — re-correlate via the platform/username fields if you need to preserve input order.
get_posts
Fetch a creator's posts, sorted and paginated. Use this when the user asks to see what a creator has posted (e.g., "show me Jane's last 20 posts", "what are this creator's top-engagement reels?", "pull recent posts from creator-id ABC"). Identify the creator by either `creator_id` (UUID) OR (`platform` + `username`). `sort` defaults to "recent" (newest first); use "top_engagement" for the highest- engagement posts, or one of "most_likes" / "most_views" / "most_comments" for a specific metric. `limit` defaults to 12 and is capped at 50. Pass `cursor` from a previous response's `next_cursor` to paginate. Returns post records (caption, media URL, like/comment/view counts, timestamps), plus `has_more` and `next_cursor` for pagination. Examples: - User: "Show @niickjackson's recent Instagram posts" -> use this tool with platform "instagram" and username "niickjackson". - User: "Is @niickjackson a fit for Pixel?" -> use this after `get_profile` when the fit analysis needs recent content evidence, then call `match_creators`.
get_instagram_post
Fetch raw Instagram post-page data by shortcode. Use this when the user needs fresh raw Instagram post metadata that is not guaranteed on regular cached post-list endpoints yet, including coauthors, tagged users, paid partnership metadata, product mentions, music attribution, location, display resources, and video versions.
get_instagram_posts
Fetch raw Instagram post-page data for a bounded list of shortcodes through the raw API. Returns one item per requested shortcode with per-item success or error details.
get_instagram_post_transcript
Transcribe an Instagram video post by shortcode through the raw API. For now this retranscribes every request. Cached transcript reads are planned as a follow-up, and public pricing is intended to stay the same for live and cached transcript delivery.
get_instagram_post_transcripts
Transcribe a bounded list of Instagram video posts by shortcode through the raw API. For now this retranscribes every request. Successful items include the raw post data used for transcription.

Is this your server?

Create a free RNWY account to connect your on-chain identity to this server. MCP server claiming is coming; register now and you'll be first in line.

Create your account →
More from influship
Influship
Find and analyze influencers with creator search, lookalikes, profiles, posts, and transcripts.
Sponsorbook
Research YouTube sponsors, inspect sponsorship evidence, and manage brand lists with Sponsorbook.
Similar servers
Press Release
press-release MCP — wraps StupidAPIs (requires X-API-Key)
MCP Server for LimeSurvey
Enables interaction with LimeSurvey API to create and manage surveys, questions, question groups, activate surveys, and export responses through standardized MCP endpoints.
io.github.zenml-io/mcp-zenml
MCP server for ZenML - browse stacks, pipelines, runs, artifacts & trigger pipeline runs via API
Linear
Linear MCP — wraps the Linear GraphQL API (OAuth)
HAPI MCP Server
HAPI MCP server: Dynamically exposes OpenAPI REST APIs as MCP tools for AI assistants
Google Docs MCP Server
Enables Claude to read, create, and update Google Docs through OAuth authentication. Deployed as a remote Next.js server on Vercel with support for multiple users and secure API key management.
Indexed from Smithery · Updates nightlyView on Smithery →