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.
概要
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.
適用範囲と境界
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.
- 適している用途
- 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 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.
失敗時の処理
作者が宣言した失敗時と再試行の動作です。連携時にはシステムプロンプトに含めることをおすすめします。
- 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.
入力
この App の呼び出しに必要なパラメータで、manifest.json の input.schema から生成されています。
| フィールド | 業務名称 | 型 | 必須 | デフォルト | 列挙値／制約 | 例 | 説明 |
|---|---|---|---|---|---|---|---|
| names_or_nicknames | Names or nicknames | array<string> | はい | — | 最大 1000 件 | ["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. |
出力
1 件のレコードのフィールド構造で、manifest.json の output.schema から生成されています。
| フィールド | 業務名称 | 型 | 例 | 説明 |
|---|---|---|---|---|
| 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
出力はレコード単位で 1 件ずつ返されます。 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
}連携方法
この App は MCP、API、SDK、ファイルエクスポートのいずれでも連携でき、どのチャネルも同じ能力と料金を共有します。すべてのリクエストは Authorization: Bearer ヘッダーで認証し、認証情報には API Key（長期有効。Open Platform コンソールで作成）を使用します。MCP クライアントは OAuth によるキー不要のログインにも対応しています。CLI や Skill など、さらに多くの連携方法も準備中です。
MCP（Model Context Protocol）を使うと、Claude や Cursor などの AI クライアントからこの App を直接呼び出せます。クライアントと認証方式を選び、下の設定をコピーしてください。
クライアント設定
Bearer の後の値を長期有効な API Key に置き換えてください。あらゆるクライアント、CI、ヘッドレス環境で利用できます。
{
"mcpServers": {
"YiJacobJohnRaku__social-media-finder": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=YiJacobJohnRaku/social-media-finder",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}AI に設定を任せる
設定を手作業で編集したくない場合は、インストールプロンプトをコピーして任意の AI クライアントに貼り付けてください。AI が自分のやり方でセットアップを完了します（プロンプトは AI があなたに API Key を尋ねる形になっているため、認証情報がチャット履歴や共有設定に残りません）。
detail.access.mcp.composeHint
料金
正常に返されたレコードの件数に応じて課金されます。失敗したタスクには課金されません。
複数の課金イベントはそれぞれ独立して累計されます。詳細は各項目をご覧ください。失敗したタスクには課金されません。
今すぐ試す
パラメータを入力して実行してください。結果は実際の呼び出しによるものです。