
Social Profile Enrichment API
io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Nov 2, 2026
Social media profile lookup for GitHub, Twitter/X, LinkedIn, YouTube. x402.
Overview
Remote MCP endpoint that looks up public social media profiles on GitHub, Twitter/X, LinkedIn and YouTube, paid per call in USDC via x402.
- What you can do
- Look up a public social profile by handle plus platform, or by full profile URL
- Return structured JSON with display name, bio, avatar, follower and following counts, post count, location and verification status
- Offer the same lookup as a GET query or a POST with a JSON body
- Serve as one entry in a larger marketplace of pay-per-call APIs for agents
- When to use it
- Useful when an assistant needs quick public profile facts for influencer research, lead enrichment, social listening, building contact profiles, or checking that a social presence is real. It is not intended for email lookup, company data or person enrichment by email.
- Requirements
- A remote MCP client pointed at the hosted endpoint; nothing to install locally. No API key or signup, but each call is paid in USDC on the Base L2 network through the x402 protocol, so the client needs an x402-aware wallet or payment handler. Network access to the provider's domain is required.
Installation
In SourceWeft
- Open Social Profile Enrichment API in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fsocial-profile/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"social-profile-enrichment-api": {
"type": "sse",
"url": "https://social-profile.api.klymax402.com/mcp"
}
}
}README
Social Profile Enrichment API
[MCP Server] [x402] [License: MIT]
Enrich social profiles from handle or URL -- Twitter/X, GitHub, LinkedIn, YouTube. Followers, bio, verification. 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.):
Quickstart -- HTTP (x402)
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
social_lookup_profile
Use this when you need public profile data from a social media handle or URL. Returns structured profile data in JSON.
Parameters
Example response:
When to use: influencer research, lead enrichment, social listening, building contact profiles, and verifying social media presence.
Not for: email lookup (use email_find_by_name), company data (use company_enrich_from_domain), person enrichment by email (use person_enrich_from_email).
social_lookup_profile
Use this when you need public profile data from a social media handle or URL. Returns structured profile data in JSON.
Parameters
Example response:
When to use: influencer research, lead enrichment, social listening, building contact profiles, and verifying social media presence.
Not for: email lookup (use email_find_by_name), company data (use company_enrich_from_domain), person enrichment by email (use person_enrich_from_email).
Example agent prompts
- "Public profile data from a social media handle or URL"
- "Public profile data from a social media handle or 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.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Source: README.md at commit f542e95
Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
50% 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 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts