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.
Übersicht
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.
Anwendungsbereich & Grenzen
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.
- Geeignet für
- 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.
- Nicht verwenden für
- 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.
Fehlerbehandlung
Vom Autor deklariertes Fehler- und Wiederholungsverhalten. Wir empfehlen, es bei der Integration in Ihren System-Prompt aufzunehmen.
- 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.
Eingabe
Parameter, die zum Aufruf dieser App erforderlich sind, generiert aus dem input.schema in der manifest.json.
| Feld | Fachlicher Name | Typ | Erforderlich | Standard | Enum / Einschränkungen | Beispiel | Beschreibung |
|---|---|---|---|---|---|---|---|
| names_or_nicknames | Names or nicknames | array<string> | Ja | — | bis zu 1000 Einträge | ["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. |
Ausgabe
Feldstruktur eines einzelnen Datensatzes, generiert aus dem output.schema in der manifest.json.
| Feld | Fachlicher Name | Typ | Beispiel | Beschreibung |
|---|---|---|---|---|
| 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. |
Datensatz-Schema
Die Ausgabe wird Datensatz für Datensatz zurückgegeben. 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
Diese App kann über MCP, API, SDK oder Dateiexport integriert werden — alle Kanäle teilen sich dieselben Fähigkeiten und Preise. Jede Anfrage authentifiziert sich über den Authorization: Bearer-Header mit einem API Key (langlebig, in der Open-Platform-Konsole erstellt); MCP-Clients können sich zusätzlich per OAuth ohne Key anmelden. Weitere Optionen wie CLI und Skill sind in Vorbereitung.
Über das MCP (Model Context Protocol) können Sie diese App direkt aus KI-Clients wie Claude und Cursor aufrufen. Wählen Sie Ihren Client und den Authentifizierungsmodus und kopieren Sie dann die Konfiguration unten.
Client-Konfiguration
Ersetzen Sie den Wert nach Bearer durch Ihren langlebigen API Key. Funktioniert in jedem Client, in CI und in Headless-Umgebungen.
{
"mcpServers": {
"YiJacobJohnRaku__social-media-finder": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=YiJacobJohnRaku/social-media-finder",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Lassen Sie die KI die Einrichtung übernehmen
Sie möchten Konfigurationen nicht von Hand bearbeiten? Kopieren Sie den Installations-Prompt und fügen Sie ihn in einen beliebigen KI-Client ein — er schließt die Einrichtung auf seine eigene Weise ab. (Der Prompt weist die KI an, Ihren API Key bei Ihnen zu erfragen, damit Zugangsdaten nie im Chatverlauf oder in geteilten Konfigurationen landen.)
detail.access.mcp.composeHint
Preise
Berechnet nach der Anzahl der erfolgreich zurückgegebenen Datensätze. Fehlgeschlagene Aufgaben werden nicht berechnet.
Mehrere Abrechnungsereignisse werden unabhängig voneinander kumuliert — Details siehe jeweilige Position. Fehlgeschlagene Aufgaben werden nicht berechnet.
Jetzt ausprobieren
Füllen Sie die Parameter aus und starten Sie — die Ergebnisse stammen aus einem echten Aufruf.