Company social handles (LinkedIn, Instagram, X, Facebook, YouTube) via Apify MCP.
One address for any MCP client. Your key stays in your Odel vault.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
| Access to | Read | Change |
|---|---|---|
| Full api access | Not stated: full_api_access | |
From the sign-in at console-backend.apify.com, as the endpoint publishes it. You approve it there.
Odel could not list its tools without signing in.
Drop-in company social profile resolution for sales and marketing software — CRMs, lead-gen tools, enrichment pipelines, and AI assistants — via Apify’s hosted MCP or the Store Actor directly.
Resolves a company name, website, or Google Maps listing to its verified LinkedIn, Instagram, X, Facebook and YouTube handles, with evidence. Manifest-only repo — no Actor source.
Disclosure: I maintain these Actors on Apify Store (publicrecords). This repo documents MCP / client config only.
https://mcp.apify.com/?tools=publicrecords/company-social-profile-finder
| Actor | Store / status | Role |
|---|---|---|
| Company Social Media Profile Finder | publicrecords/company-social-profile-finder (listed) | Resolve name / website / Maps place → LinkedIn, Instagram, X, Facebook, YouTube (+ evidence) |
Use either path:
Auth: your own Apify token in the client when prompted. Runs are billed on your Apify account.
| Event | USD |
|---|---|
actor-start | $0.005 |
entity-resolved (primary) | $0.02 |
identity-change | $0.01 |
Measured proof: apify.com → run dqgG9vmZuLevEMQ3T — 5 confident / 4 confirmed handles (2026-09-28).
Live tools/list against the pin URL (Bearer Apify token). Tool names exposed:
| Tool name | Role |
|---|---|
publicrecords--company-social-profile-finder | Run Company Social Media Profile Finder (publicrecords/company-social-profile-finder) |
get-actor-run | Get detailed information about a specific Actor run |
get-dataset-items | Read items from a run dataset |
get-key-value-store-record | Read a key-value store record |
abort-actor-run | Abort a running Actor run |
Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"company-social": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--actors",
"publicrecords/company-social-profile-finder"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN"
}
}
}
}
Or point the Apify remote MCP URL (with the pin above) if your Claude Desktop build supports remote MCP servers.
In Cursor MCP settings / .cursor/mcp.json:
{
"mcpServers": {
"company-social": {
"url": "https://mcp.apify.com/?tools=publicrecords/company-social-profile-finder"
}
}
}
Sign in with Apify when Cursor prompts.
Prompt: Which social profiles belong to apify.com?
Expected: LinkedIn / Instagram / X / Facebook / YouTube handles with confidence + evidence (see proof run dqgG9vmZuLevEMQ3T).
Prompt: Resolve social handles for these domains: stripe.com, notion.so. Return confident LinkedIn and X only.
Tool call the agent makes (publicrecords--company-social-profile-finder):
{ "queries": ["stripe.com", "notion.so"], "mode": "resolve" }
MIT — applies to this documentation and config only.
Published by the publicrecords maintainer on Apify.