Person Social Footprint Mapper MCP Server

An MCP server for the Mamba Labs Person Social Footprint Mapper actor on Apify. Give it a person's full name and the domain of the company they work at. Each run returns one row with that person's public GitHub, Bluesky, personal site, Substack, and X profiles, with a status and a match confidence per platform.

What's Inside

• What it does

• Quick start

• Prerequisites

• Example prompts

• Tool

• Inputs

• Pricing

• Your keys

• Full actor documentation

• License

Related MCP server: social-profile

What it does

Find a person's public profiles from a name and a company domain. You get one row per person with the GitHub profile, Bluesky profile, personal website, Substack newsletter, and X profile, each with public follower counts where the platform shows them, a status (found, ambiguous, not_found, skipped, skipped_rate_limit, blocked), and a confidence from 0 to 1.

A profile is found only at 0.8 or more, which needs evidence that ties it to the company or to another profile of the same person: a link to the company domain, the company's own team page listing it, the GitHub company field or organization membership, or two profiles that link to each other. A matching name alone is never enough, and a likely match that is not certain comes back ambiguous with no handle. No email address or phone number is ever returned, LinkedIn is never opened, and Substack is never read.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-person-social-footprint-mapper": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-person-social-footprint-mapper"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The map_person_social_footprint tool appears.

Prerequisites

• Node.js 18 or newer.

• An Apify API token from console.apify.com/account/integrations, set as APIFY_TOKEN. The server lists its tool without a token; a call needs one.

• Optional: GITHUB_TOKEN, your own free GitHub token, for batches larger than a few dozen persons.

• Optional: X_BEARER_TOKEN, your own X API bearer token. Without it the X columns return skipped.

Example prompts

• "Find Mitchell Hashimoto's public GitHub and Bluesky profiles. He founded hashicorp.com."

• "For these five founders and their company domains, which have a personal site or a newsletter?"

• "Does the CTO of hubspot.com have a public GitHub profile?"

Tool

map_person_social_footprint. One tool. Example arguments:

{
  "full_name": "Mitchell Hashimoto",
  "company_domain": "hashicorp.com"
}

Inputs

Every buyer facing input of the actor. Omitted inputs take the actor's own defaults. Give full_name with company_domain, or persons. The two keys are read from this server's environment, never from tool arguments.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

A person with nothing found, and blocked and error rows, are free. Mamba Labs pays the platform costs of the run, Apify proxy traffic included.

Your keys

The actor stores no key. GITHUB_TOKEN and X_BEARER_TOKEN are optional and are your own: this server reads them from its environment and sends them in the run input of that run only. X bills each X lookup to your own X account. With no X key, X is never contacted.

Responsible use

GitHub's Acceptable Use Policies do not allow its users' information to be used for spam, unsolicited email, or selling personal information, for example to recruiters, headhunters, and job boards. You are the data controller for the rows you collect under GDPR, CCPA, and applicable privacy laws.

Full actor documentation

apify.com/mambalabs/person-social-footprint-mapper

License

MIT. See LICENSE.