Skip to content
Walletlink.social logo

Walletlink.social MCP server

Which servers in the official MCP registry are Walletlink.social's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to Walletlink.social

Whose server it is
  • Registry namesocial.walletlink/wallet-identityverified in the MCP registry

The registry name sits under walletlink.social. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools8
  • Server calls itselfwalletlink.social
  • Server version1.4.1
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 182 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Turn a wallet list into matching X and Farcaster accounts; Find the wallets behind a given X or Farcaster handle.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "Turn a wallet list into matching X and Farcaster accounts", the likely first call is walletlink_resolve_wallets.
  • For "Find the wallets behind a given X or Farcaster handle", the likely first call is walletlink_wallets_by_x_handle.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-20
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it2 of 2 use cases
  • Use1 GitHub stars
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer333 ms
  • Space in an agent's context≈ 2,535 tokensthe definitions of all its tools (8), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Turn a wallet list into matching X and Farcaster accounts
  • can do · Find the wallets behind a given X or Farcaster handle
  • not sure · Check how many holders carry a social handle

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers8 tools · read 2026-10-20
  • walletlink_resolve_wallets

    Resolve one or more Ethereum addresses to the social identities attached to them: X handle, Farcaster account, ENS name, Lens profile, GitHub account. COST: one match credit per address that resolves to an X handle or a Farcaster account…

  • walletlink_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 attested come back, so a wallet whose attested link sits beside a correlated source is left out…

  • walletlink_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 whose Farcaster verification sits beside a correlated source is left out; resolving that address…

  • walletlink_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 meters. It resolves no wallet and consumes no rate limit. A key whose balance is zero can still read…

  • walletlink_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 before a reverse lookup, which can spend up to 100 credits in one go. matches_available is the meter…

  • walletlink_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 holds only stale answers for, is resolved against live sources, so a job can find identities the…

  • walletlink_job_status

    Progress and results for a job submitted with walletlink_submit_job. While the job runs it reports processed counts; on completion it reports the resolved records and what was billed. COST: free on both meters, so a drained key can still…

  • walletlink_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 band a resolve would bill inside. Counts only, no identities. Use it to decide whether a list is…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "wallet-identity": {
      "type": "http",
      "url": "https://walletlink.social/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http walletlink https://walletlink.social/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://walletlink.social/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.