Back to Browse

Person Enrichment X402 MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Person lookup from email: name, title, company, social profiles. x402.

About

Person lookup from email: name, title, company, social profiles. x402.

Remote endpoints: sse: https://person-enrichment.api.klymax402.com/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (155/159 approved); 5 highly-trusted packages.

1 tool verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

database

Check that this permission is expected for this type of plugin.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-br0ski777-person-enrichment": {
      "url": "https://person-enrichment.api.klymax402.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Person Enrichment API

MCP Server x402 License: MIT

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.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "person-enrichment": {
      "url": "https://person-enrichment.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

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.

Tools

ToolMethodPathPriceDescription
person_enrich_from_emailGET/api/enrich$0.02Enrich a person profile from their email address
person_enrich_from_emailPOST/api/enrich$0.02Enrich a person profile from their email address

person_enrich_from_email

Enrich 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

NameTypeRequiredDescription
emailstringyesEmail 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_email

Enrich 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

NameTypeRequiredDescription
emailstringyesEmail 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).

Example agent prompts

  • "Enrich a person's profile with additional data from their email address, name, domain, or LinkedIn URL"
  • "Enrich a person's profile with additional data from their email address, name, domain, or LinkedIn URL"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Reviews

No reviews yet

Be the first to review this server!