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.
Descripción general
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.
Alcance y límites
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.
- Adecuada para
- 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.
- No usar para
- 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.
Gestión de fallos
Comportamiento de fallos y reintentos declarado por el autor. Recomendamos incluirlo en tu prompt del sistema al integrar.
- 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.
Entrada
Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.
| Campo | Nombre de negocio | Tipo | Obligatorio | Predeterminado | Enum / Restricciones | Ejemplo | Descripción |
|---|---|---|---|---|---|---|---|
| names_or_nicknames | Names or nicknames | array<string> | Sí | — | hasta 1000 elementos | ["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. |
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
| Campo | Nombre de negocio | Tipo | Ejemplo | Descripción |
|---|---|---|---|---|
| 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. |
Schema del registro
La salida se devuelve registro a registro. 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
}Integración
Esta App se puede integrar mediante MCP, API, SDK o exportación de archivos — todos los canales comparten las mismas capacidades y precios. Cada solicitud se autentica con la cabecera Authorization: Bearer usando una API Key (de larga duración, creada en la consola de Open Platform); los clientes MCP también pueden iniciar sesión con OAuth sin clave. Más opciones como CLI y Skill están en camino.
Con MCP (Model Context Protocol) puedes llamar a esta App directamente desde clientes de IA como Claude y Cursor. Elige tu cliente y el modo de autenticación, y copia la configuración de abajo.
Configuración del cliente
Sustituye el valor tras Bearer por tu API Key de larga duración. Funciona en cualquier cliente, CI o entorno sin interfaz.
{
"mcpServers": {
"YiJacobJohnRaku__social-media-finder": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=YiJacobJohnRaku/social-media-finder",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Deja que la IA lo configure por ti
¿No quieres editar configuraciones a mano? Copia el prompt de instalación y pégalo en cualquier cliente de IA: completará la configuración a su manera. (El prompt le pide a la IA que te solicite tu API Key, de modo que las credenciales nunca queden en el historial de chat ni en configuraciones compartidas.)
detail.access.mcp.composeHint
Precios
Se cobra según el número de registros devueltos correctamente. Las tareas fallidas no se cobran.
Los distintos eventos de facturación se acumulan de forma independiente — consulta cada elemento para más detalles. Las tareas fallidas no se cobran.
Pruébalo ahora
Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.