Developer Tools
walletlink.social
Provides a database of Ethereum wallet addresses linked to social identities like X and Farcaster, enabling lookups by address or handle.
ENDPOINT 1
https://walletlink.social/api/mcp
MCP server metadata
- Name
- walletlink.social
- Version
- 1.4.0
This server answers two questions about an Ethereum address: which social accounts its owner published, and which addresses a given X handle or Farcaster account is attested to. Balances, transfers and prices are a block explorer’s job. An identity is attested when the wallet owner published the link themselves: a Farcaster verification, an onchain ENS record, an attested-social sign-in, or a manually verified record. Anything else is correlated, and labeled so. Nothing is inferred from a display name or a bio. A match is a wallet resolved to an X handle or a Farcaster account. Wallets that resolve to nothing, and wallets carrying only an ENS name, a Lens profile or a GitHub account, are never billed. Billing is per address, not per identity: an address carrying both an X handle and a Farcaster account costs one credit. An unpromising list is cheap to try, and splitting one saves no credits. The ceiling is 50 addresses per call on the default plan; a live Scale or Index pack raises it (the balance tool reports yours). The reverse direction is the expensive one: one page of the wallets behind a handle can spend 100 credits, and the free allowance is 100 matches per 30 days. Reading the balance, the coverage figures or a list estimate costs no credits. A key whose balance is zero can still read the free endpoints; the balance and coverage reads keep answering at zero, and only a call that could bill refuses with NO_CREDITS. A checked X handle carries one of four states: live, suspended, unclaimed, or reassigned. A handle can be attested by its owner and suspended today, so a handle is not a promise that anyone is behind it. A field that is absent was not measured. Absent is not false: a missing reachability means the handle was not checked, never that nobody is behind it.
Known tools 8
walletlink_resolve_walletsResolve one or more Ethereum addresses to the social identities attached to them: X handle, Farcaster account, ENS name, Lens profile, GitHub account.
Inferred read-onlywalletlink_wallets_by_x_handleFind the wallets in the index attested to an X account.
Inferred read-onlywalletlink_wallets_by_farcaster_usernameFind the wallets in the index attested to a Farcaster account.
Inferred read-onlywalletlink_account_balanceHow many match credits the configured key has left, and how much of the request allowance it has used.
Inferred read-onlywalletlink_job_statusProgress and results for a job submitted with walletlink_submit_job.
Inferred read-onlywalletlink_estimate_listA 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 band a resolve would bill inside.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.walletlink-social]
url = "https://walletlink.social/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"walletlink-social": {
"type": "http",
"url": "https://walletlink.social/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: walletlink-social
Remote MCP URL: https://walletlink.social/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"walletlink-social": {
"url": "https://walletlink.social/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"walletlink-social": {
"type": "http",
"url": "https://walletlink.social/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "walletlink-social",
"transport": "streamable-http",
"url": "https://walletlink.social/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.