Person Social Footprint Mapper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. Required for tool calls. | |
| GITHUB_TOKEN | No | Optional: your own free GitHub token, for batches larger than a few dozen persons. | |
| X_BEARER_TOKEN | No | Optional: your own X API bearer token. Without it the X columns return skipped. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| map_person_social_footprintA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlapping purpose. Its scope (name + company domain in, profile URLs/confidences out) is unambiguous.
The single name map_person_social_footprint follows a clear snake_case verb_noun_resource pattern and is fully self-consistent. No mixed conventions exist to cause confusion.
A single tool for a single-purpose, batch-style operation is defensible, but it is thin: there is no separate way to fetch a prior run, check quota/rate-limit state, or process people in bulk. One tool of this complexity sits at the borderline of the 3-15 range.
The core lookup is covered, but the surface has notable gaps: errors return a run ID with no tool to retrieve or re-inspect that run, there is no batch/multi-person variant, and no way to re-run or filter without re-billing. Agents can work around these by re-calling, but it is not a complete lifecycle.