Person lookup from email: name, title, company, social profiles. x402.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"person-enrichment": {
"url": "https://person-enrichment.api.klymax402.com/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Person enrichment from email. Full name, job title, company, LinkedIn, GitHub, Twitter, avatar, location. Ideal for lead research. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
One local source for the MCP servers, tools, and memory your AI coding agents share, synced into each tool's native config with a review gate and a receipt for every change. No daemon, no lock-in.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Br0ski777/person-enrichment and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Person enrichment from email. Full name, job title, company, LinkedIn, GitHub, Twitter, avatar, location. Ideal for lead research. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"person-enrichment": {
"url": "https://person-enrichment.api.klymax402.com/mcp"
}
}
}
curl "https://person-enrichment.api.klymax402.com/api/enrich?email=user@example.com"
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
person_enrich_from_email | GET | /api/enrich | $0.02 | Enrich a person profile from their email address |
person_enrich_from_email | POST | /api/enrich | $0.02 | Enrich a person profile from their email address |
person_enrich_from_emailEnrich a person's profile with additional data from their email address, name, domain, or LinkedIn URL. Alternative to Apollo people-enrich at 5x lower cost. Returns structured JSON with full contact and professional details.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
email | string | yes | Email address to enrich (e.g. john@company.com) |
Example response:
{"fullName":"Jane Smith","jobTitle":"VP Engineering","company":"Acme Corp","linkedin":"https://linkedin.com/in/janesmith","github":"https://github.com/janesmith","location":"San Francisco, CA","avatar":"https://gravatar.com/abc123","domain":"acme.com"}
When to use: outreach to personalize emails, enrich CRM records, search for people/contacts, or research decision-makers. Essential for sales prospecting, lead qualification, and account mapping. Drop-in replacement for Apollo person enrichment.
Not for: email validation (use email_verify_address), company data (use company_enrich_from_domain), social profiles by username (use social_lookup_profile), finding email addresses (use email_find_by_name).
person_enrich_from_emailEnrich a person's profile with additional data from their email address, name, domain, or LinkedIn URL. Alternative to Apollo people-enrich at 5x lower cost. Returns structured JSON with full contact and professional details.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
email | string | yes | Email address to enrich (e.g. john@company.com) |
Example response:
{"fullName":"Jane Smith","jobTitle":"VP Engineering","company":"Acme Corp","linkedin":"https://linkedin.com/in/janesmith","github":"https://github.com/janesmith","location":"San Francisco, CA","avatar":"https://gravatar.com/abc123","domain":"acme.com"}
When to use: outreach to personalize emails, enrich CRM records, search for people/contacts, or research decision-makers. Essential for sales prospecting, lead qualification, and account mapping. Drop-in replacement for Apollo person enrichment.
Not for: email validation (use email_verify_address), company data (use company_enrich_from_domain), social profiles by username (use social_lookup_profile), finding email addresses (use email_find_by_name).