Social Media Profile Finder
Find possible public social media profile URLs associated with submitted names or nicknames, with the source name and platform retained in each record.
Overview
Social Media Profile Finder turns a list of names, nicknames, handles, or brand names into a structured review set of possible public profiles. Each result keeps the submitted value beside a social-platform label and the profile address returned for that search, making scattered profile-search results easier to compare in one place.
The dataset is designed for discovery and triage rather than identity confirmation. It can help researchers, brand-protection teams, recruiters, and creator-research teams assemble candidates for further review while preserving the exact search value that produced each result. Keeping that context attached is especially useful when the same nickname appears on several platforms or belongs to multiple people.
Data notes
Records come from publicly searchable profile surfaces supported by the source workflow. Each record represents the outcome for one submitted value on one reported social platform. A returned profile address is a possible match, not proof that the profile belongs to the intended person, organization, or brand. The same submitted value can therefore produce multiple platform records, and every candidate should be independently reviewed before it is used for outreach, screening, enforcement, or attribution.
“Profile URL” can contain the literal value None when a platform row is returned without a matched address. Such rows are retained because they show which submitted value and platform were checked; they should not be treated as discovered profiles. Private, deleted, restricted, and sign-in-only profiles are outside the dataset’s public-search scope. Availability can also change as platforms and public profiles change.
What the results look like
Each record is one submitted value paired with a reported platform and its candidate profile address or no-match marker:
| Submitted name | Social platform | Profile URL |
|---|---|---|
| 1 | GitHub | https://github.com/1 |
| 1 | Medium | None |
| 1 | Twitch | https://www.twitch.tv/Ssaab |
Use cases
- For cross-platform name research, group rows by “Submitted name” and compare “Social platform” with “Profile URL” to see where possible public profiles were returned.
- For candidate review queues, filter out
Nonein “Profile URL,” then open the remaining addresses and verify whether their visible details match the intended subject. - For brand or handle monitoring, rerun the same “Submitted name” values at different times and compare “Social platform” and “Profile URL” to identify newly returned or changed candidates.
- For collision analysis, compare repeated “Submitted name” values against their “Profile URL” results to flag names that require additional evidence before attribution.
Scope & Boundaries
Each run accepts 1 to 1,000 names or nicknames and searches supported public profile surfaces; retrieval is capped at 10,000 returned records per run.
- Good for
- Use it when you need possible public profile URLs associated with one or more names, nicknames, handles, or brand names.
- Use it to build a review list that keeps each submitted value connected to the platform and candidate profile URL returned for it.
- Do not use for
- Do not use it as proof that a returned profile belongs to a specific person or organization; candidate matches require independent verification.
- Do not use it for private, deleted, restricted, or sign-in-only profiles because only publicly searchable profile surfaces are covered.
Failure Handling
Failure and retry behavior declared by the author. We recommend including it in your system prompt when integrating.
- 1If a run stops before completion, retry the same small input once; if it stops again, split a large name list into smaller runs.
- 2A missing profile URL can mean no public candidate was found for that name and platform or access was temporarily limited; review other returned platforms and retry later if needed.
Input
Parameters required to call this app, generated from the input.schema in manifest.json.
| Field | Business name | Type | Required | Default | Enum / Constraints | Example | Description |
|---|---|---|---|---|---|---|---|
| names_or_nicknames | Names or nicknames | array<string> | Yes | — | up to 1000 items | ["1"] | Names, nicknames, handles, or brand names to search across supported public profile surfaces. Enter 1 to 1,000 values, with one value per item. |
Output
Field structure of a single record, generated from the output.schema in manifest.json.
| Field | Business name | Type | Example | Description |
|---|---|---|---|---|
| input_name | Submitted name | string | 1 | Original name or nickname submitted for the profile search. |
| social_media | Social platform | string | GitHub | Platform label associated with the profile-search result. |
| profile_url | Profile URL | string | https://github.com/1 | Candidate public profile address returned for the submitted name and platform, or the literal value None when no address was returned. |
Record Schema
Output is returned record by record. detail.output.idFieldHint
{
"type": "object",
"properties": {
"input_name": {
"type": "string",
"title": "Submitted name",
"description": "Original name or nickname submitted for the profile search.",
"prefill": "1"
},
"social_media": {
"type": "string",
"title": "Social platform",
"description": "Platform label associated with the profile-search result.",
"prefill": "GitHub"
},
"profile_url": {
"type": "string",
"title": "Profile URL",
"description": "Candidate public profile address returned for the submitted name and platform, or the literal value None when no address was returned.",
"prefill": "https://github.com/1"
}
},
"required": [],
"additionalProperties": false
}Integration
This app can be integrated via MCP, API, SDK, or file export — all channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API Key (long-lived, created in the Open Platform console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way.
With the MCP (Model Context Protocol), you can call this app directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.
Client config
Replace the value after Bearer with your long-lived API Key. Works in any client, CI, or headless environment.
{
"mcpServers": {
"YiJacobJohnRaku__social-media-finder": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=YiJacobJohnRaku/social-media-finder",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Let AI set it up for you
Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client — it will complete the setup its own way. (The prompt asks the AI to request your API Key from you, so credentials never end up in chat history or shared configs.)
detail.access.mcp.composeHint
Pricing
Charged by the number of records successfully returned. Failed tasks are not charged.
Multiple billing events accumulate independently — see each item for details. Failed tasks are not charged.
Try It Now
Fill in the parameters and run — results come from a real call.