Categories › Communication › Social media
Resolve wallet addresses to X and Farcaster accounts, and back again.
Remote server: your requests and data go to walletlink.social. Claude Code: claude mcp add --transport http walletlink-social https://walletlink.social/api/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
walletlink_resolve_wallets — Resolve one or more Ethereum addresses to the social identities attached to them: X handle, Farcaster account, ENS name, Lens profile, GitHuwalletlink_wallets_by_x_handle — Find the wallets in the index attested to an X account. The reverse of resolving an address. Only wallets whose recorded sources are all attwalletlink_wallets_by_farcaster_username — Find the wallets in the index attested to a Farcaster account. Only wallets whose recorded sources are all attested come back, so a wallet wwalletlink_index_coverage — How much of the index carries each identity type. Use it to judge whether a lookup is worth making before making it. COST: free on both metewalletlink_account_balance — How many match credits the configured key has left, and how much of the request allowance it has used. COST: free on both meters. Call it bewalletlink_submit_job — Submit a list of addresses as a background job. A job runs a deeper scan than the resolve tool: an address the index has not checked, or holwalletlink_job_status — Progress and results for a job submitted with walletlink_submit_job. While the job runs it reports processed counts; on completion it reportwalletlink_estimate_list — A dry run over a list of addresses: how many are in the index, how many were checked and found bare, how many have never been seen, and the Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.