Person Enrichment MCP
Pricing
Pay per usage
Person Enrichment MCP
MCP server that turns an email, a LinkedIn URL or a sentence about someone into one verified profile of the person and their company, with conflicts between sources spelled out instead of guessed.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Theona
Maintained by CommunityActor stats
1
Bookmarked
1
Total users
0
Monthly active users
a day ago
Last modified
Categories
Share
An MCP server that identifies a person from partial information and returns one structured profile.
Give the tool whatever you know about someone — a name, an email, a LinkedIn URL, or a sentence like "the CTO of Acme who spoke at re:Invent" — and it returns what could actually be verified. Every field carries a confidence score from 0 to 1 and names its source. Anything it could not establish is left out rather than guessed. When two sources disagree, it keeps the one it trusts, lowers the confidence and records the disagreement. When more than one real person fits, it returns the candidates instead of choosing.
It reads only: it connects to nothing of yours and writes nothing anywhere. It returns no home addresses, personal phone numbers or family details, even where a source offers them — only what a person has published about themselves professionally, or what a business data provider publishes about them in that capacity.
Tool
person_enrichment — takes query (the text or identifier you have) and returns one JSON object:
| Field | Meaning |
|---|---|
status | found, ambiguous, no_match or insufficient_input |
person | The profile, each field with its confidence and source |
company | The person's current company |
signals | Notable recent activity |
conflicts | Where sources disagreed, and which value was kept |
candidates | Every plausible match, when the input fits more than one person |
notes | What was attempted |
queried_at | When the lookup ran |
Credentials
Two are needed:
- Your Apify API token, in the
Authorizationheader, as for any Apify MCP server. - Your Theona access key, in the
X-Theona-Api-Keyheader. The lookup runs on your own Theona account. Get the key at app.theona.ai/mcp; it opens this one agent and can be revoked on the same page.
Claude Code
claude mcp add --transport http person-enrichment \https://theona--person-enrichment-mcp.apify.actor/mcp \--header "Authorization: Bearer <APIFY_TOKEN>" \--header "X-Theona-Api-Key: <THEONA_ACCESS_KEY>"
Clients that accept custom headers
{"mcpServers": {"person-enrichment": {"url": "https://theona--person-enrichment-mcp.apify.actor/mcp","headers": {"Authorization": "Bearer <APIFY_TOKEN>","X-Theona-Api-Key": "<THEONA_ACCESS_KEY>"}}}}
Costs
Apify bills the platform usage of the Standby run. Lookups count against your Theona plan.
Support
Open an issue on this Actor's Issues tab.