Mcp Person Social Footprint Mapper

com.mambabuiltPublished by mambabuilt.comv1.0.1Updated Nov 7, 2026

Find a person's public GitHub, Bluesky, personal site, Substack, and X profiles by name and company

The publisher's own server: person.work — Agent-maintained CV

Overview

AI-generated overview

Looks up a person's public GitHub, Bluesky, personal site, Substack and X profiles from their full name and company domain, via an Apify actor.

What you can do
  • Map a person's public profiles from a full name plus company domain, or a batch of up to 200 persons per run
  • Return one row per person with GitHub, Bluesky, personal site, Substack and X profile URLs and public follower counts
  • Report a per-platform status (found, ambiguous, not_found, skipped, skipped_rate_limit, blocked) and a 0-1 confidence score
  • Limit the lookup to chosen platforms, add a location hint, suppress specific profile URLs, or set a cost cap
When to use it
Useful for research on founders, executives or other named individuals where you want their public professional profiles tied to a company, for example checking whether a CTO has a public GitHub account or which founders have a personal site or newsletter.
Requirements
Runs locally as an npm package via npx, needing Node.js 18 or newer. Requires an Apify account and an APIFY_TOKEN environment variable; the tool is listed without it but calls fail. Optional GITHUB_TOKEN for larger batches and optional X_BEARER_TOKEN, without which X is skipped.
Before you install
Runs are billed per event to your Apify account (per person mapped plus a per-run start fee), so set max_charge_usd if cost matters. GITHUB_TOKEN and X_BEARER_TOKEN are sent in the run input, and X lookups are billed to your own X account. It collects personal data about named individuals; the README notes GitHub's acceptable-use limits on spam and selling personal information and that you are the data controller under GDPR/CCPA.

Installation

In SourceWeft

  1. Open Mcp Person Social Footprint Mapper in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Person Social Footprint Mapper MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[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

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:

json
{  "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:

json
{  "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.

InputTypeRequiredDescription
full_namestringnoFirst and last name, for example Mitchell Hashimoto.
company_domainstringnoThe company the person works at, for example hashicorp.com.
personsarraynoSeveral persons, one per entry as Full Name | company.com. Up to 200 per run.
linkedin_urlstringnoA weak hint from the words in the URL. LinkedIn is never opened.
locationstringnoCity or country, a small boost when a profile agrees.
platformsarraynoAny of github, bluesky, personal_site, substack, x. Omit for all five.
suppress_profile_urlsarraynoProfile URLs never to return.
max_charge_usdstringnoOptional cost cap for the run.
proxy_modestringnoauto or direct. Default auto.

Pricing

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

EventFree planBronzeSilverGold
person-mapped, per person with at least one profile found$0.005$0.00475$0.0045$0.00425
apify-actor-start, per run start$0.0002$0.0002$0.0002$0.0002

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.

Source: README.md at commit 8f109b8

Tools

1

map_person_social_footprint

Map a person's social footprint

Find a person's public GitHub, Bluesky, personal site, Substack, and X profiles from their full name and the domain of the company they work at. Returns one row per person with each profile URL, public follower counts, and a status (found, ambiguous, not_found, skipped, skipped_rate_limit, blocked) and a match confidence per platform. A profile counts as found only at 0.8 confidence or more, which needs a link to the company, the company's own team page, or a link to another profile of the same person; a name match alone is never enough. No emails, no phone numbers, LinkedIn is never opened, Substack is never read. X is used only when X_BEARER_TOKEN is set in this server's environment. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN and is billed per person with at least one profile found.

Parameterspersonslocationfull_nameplatformsproxy_modelinkedin_urlcompany_domainmax_charge_usdsuppress_profile_urls

Version history

2
  1. v1.0.1LatestNov 5, 2026
  2. v1.0.0Oct 20, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Person integrations