# walletlink.social (remote · walletlink.social)

Resolve wallet addresses to X and Farcaster accounts, and back again.

- Trust score: 92/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `walletlink.social`: 92/100 (this document), [markdown](https://verifymcp.io/servers/social-walletlink-wallet-identity/api-mcp.md), [page](https://verifymcp.io/servers/social-walletlink-wallet-identity/api-mcp)

## Channel facts

- Endpoint: `https://walletlink.social/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2091 tokens (~261/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the walletlink.social MCP server?

walletlink.social is a hosted endpoint at https://walletlink.social/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http social-walletlink-wallet-identity 'https://walletlink.social/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "social-walletlink-wallet-identity": {
      "url": "https://walletlink.social/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.social-walletlink-wallet-identity]
url = "https://walletlink.social/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "social-walletlink-wallet-identity": {
      "type": "remote",
      "url": "https://walletlink.social/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add social-walletlink-wallet-identity --url 'https://walletlink.social/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  social-walletlink-wallet-identity:
    url: "https://walletlink.social/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "social-walletlink-wallet-identity": {
      "Transport": "http",
      "Url": "https://walletlink.social/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add social-walletlink-wallet-identity -t streamable-http -u 'https://walletlink.social/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 92, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 91, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-16 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `walletlink_resolve_wallets` (~355 tokens)

Resolve wallets to social identities

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. An address that resolves to nothing is free, and so is one carrying only an ENS name, a Lens profile or a GitHub account. Up to 50 addresses per call on the default plan; a live Scale pack raises the ceiling to 200 and Index to 1000, and the API refuses over YOUR ceiling with BATCH_SIZE_EXCEEDED naming it. A batch call spends one request-unit per address of the per-minute window, and a full batch fills most of a minute on every plan: the default plan gives 60 units per minute and 50-address batches, and a live Scale or Index pack raises both. Pace multi-batch runs a minute apart and read the reset time from the quota.

Each identity reports whether the address owner attested it rather than it being correlated by a third party, and each X handle reports whether it still reaches anyone: a handle can be attested and suspended, or freed and since taken by a stranger.

Send every address you need in one call. Duplicates are removed before you are charged, but each copy still costs throughput.

A retried call bills again: duplicates are removed inside one call, never across calls, and a tool call cannot carry an idempotency key. Before resending a call that may have gone through, read the balance instead of guessing.

Input parameters:

- `addresses` (array, required): Ethereum addresses, each 0x followed by 40 hex characters. Case does not matter.

### `walletlink_wallets_by_x_handle` (~196 tokens)

Find wallets behind an X handle

Find every wallet in the index attested to an X account. The reverse of resolving an address.

COST: one match credit per wallet returned, and a page holds up to 100. A handle nobody holds returns an empty list and is free. The free allowance is 100 matches per 30 days, so a single widely held handle can spend all of it in one call. Check the balance first with walletlink_account_balance if that matters. A retried call bills its returned wallets again.

Results are ordered by Farcaster follower count, highest first. When more_pages is true, pass next_cursor back to continue.

Input parameters:

- `cursor` (string): The next_cursor from a previous call, passed back unchanged. Omit for the first page.
- `handle` (string, required): An X handle, 1 to 15 letters, numbers or underscores. A leading @ is accepted. Case does not matter.

### `walletlink_wallets_by_farcaster_username` (~186 tokens)

Find wallets behind a Farcaster username

Find every wallet in the index attested to a Farcaster account.

COST: one match credit per wallet returned, and a page holds up to 100. A username nobody holds returns an empty list and is free. A retried call bills its returned wallets again.

Pass the username whole, including any .eth suffix: an ENS name attached to a Farcaster account is a large share of the index, and stripping the suffix will find nothing. Results are ordered by follower count, highest first.

Input parameters:

- `cursor` (string): The next_cursor from a previous call, passed back unchanged. Omit for the first page.
- `username` (string, required): A Farcaster username, such as dwr or vitalik.eth. 1 to 32 characters of letters, numbers, dots and hyphens, starting with a letter or a number.

### `walletlink_index_coverage` (~148 tokens)

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 the free endpoints; the balance and coverage reads keep answering at zero, and only a call that could bill refuses with NO_CREDITS.

addresses_with_an_identity over addresses_checked is the coverage rate. The second number is larger because it counts addresses we have looked at and found bare. The counts are refreshed daily rather than counted live; as_of says when they were taken, and asking twice in a day returns the same numbers.

### `walletlink_account_balance` (~118 tokens)

Match credit 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 that stops a metered call: at zero, the resolve and reverse tools refuse, while this tool and the coverage tool keep answering, so a drained key can always read its own meter. rate_limit_units_used is a separate count of requests and is not a credit figure.

### `walletlink_submit_job` (~288 tokens)

Submit a background lookup 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 resolve tool reports as never seen. Use it for lists larger than one resolve call, or when misses are worth re-checking.

COST: billed on matches exactly like resolving, when the job completes: one match credit per address that resolved to an X handle or a Farcaster account, misses free. One job may be active per account at a time; a second submission is refused until the first finishes, and the refusal names the active job id. A submission is capped at 10 times the match balance, so the worst case is bounded by what the account already holds. Submitting itself spends one request-unit of the rate window.

The submission returns a job id. Poll walletlink_job_status for progress and, on completion, the results. A job that fails is never billed.

Resubmitting the same list after a job completes runs the whole job again and bills its matches again.

Input parameters:

- `addresses` (array, required): Ethereum addresses, each 0x followed by 40 hex characters. Case does not matter. The ceiling is the balance-derived cap, not a fixed number; a list over the cap is refused with the cap named.

### `walletlink_job_status` (~166 tokens)

Check a background job

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 collect results it already paid for. 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.

Only jobs submitted by this account are visible; any other id answers not found.

Input parameters:

- `job_id` (string, required): The job id returned by walletlink_submit_job.
- `offset` (integer): Result row to start from, for a completed job. Pass the next_offset from a previous call to continue. Omit for the first page.

### `walletlink_estimate_list` (~246 tokens)

Estimate a list before spending on it

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 worth resolving, and which tool to spend on.

COST: free on the match meter, always, even at zero balance. It weighs the rate window exactly like resolving the same list (one request-unit per address), so it previews a batch at the batch’s own pace. Minimum 10 distinct addresses, because the counts are aggregates by design; the ceiling is your plan’s batch ceiling.

Reading the band: low is exact for resolving this list now (the addresses already holding an X handle or a Farcaster account). high adds never-checked addresses at the measured overall rate; a background job resolves those against live sources, a plain resolve does not. Match rates differ several-fold by chain; the coverage tool and /v1/stats carry the measured per-chain table.

Input parameters:

- `addresses` (array, required): Ethereum addresses, each 0x followed by 40 hex characters. Case does not matter.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/social-walletlink-wallet-identity/api-mcp#diagnostics

## Score history

- 2026-09-20: 92
- 2026-09-19: 91
- 2026-09-18: 91
- 2026-09-17: 90
- 2026-09-16: 90
- 2026-09-15: 89
- 2026-09-14: 89
- 2026-09-13: 89
- 2026-09-12: 88
- 2026-09-11: 88
- 2026-09-10: 87
- 2026-09-09: 87
- 2026-09-08: 86
- 2026-09-07: 86
- 2026-09-06: 85
- 2026-09-05: 85
- 2026-09-04: 84
- 2026-09-03: 84
- 2026-09-02: 83
- 2026-09-01: 83
- 2026-08-31: 82
- 2026-08-30: 83
- 2026-08-29: 83
- 2026-08-28: 82
- 2026-08-27: 82
- 2026-08-26: 81
- 2026-08-25: 79
- 2026-08-24: 65

## Common questions

### What is the walletlink.social MCP server?

walletlink.social is an MCP server listed in the public MCP registry as social.walletlink/wallet-identity. Resolve wallet addresses to X and Farcaster accounts, and back again. This page covers its hosted endpoint (https://walletlink.social/api/mcp).

### Is the walletlink.social MCP server safe to use?

walletlink.social scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the walletlink.social MCP server expose?

walletlink.social exposes 8 tools: walletlink_resolve_wallets, walletlink_wallets_by_x_handle, walletlink_wallets_by_farcaster_username, walletlink_index_coverage, walletlink_account_balance, and 3 more. Their descriptions and schemas cost roughly 1,703 tokens of context every time the server is loaded.

### Does the walletlink.social MCP server require authentication?

Yes. walletlink.social asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the walletlink.social MCP server still maintained?

walletlink.social is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://walletlink.social/api/mcp
- Repository: https://github.com/starl3xx/wallet-to-social
- Website: https://docs.walletlink.social/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/social-walletlink-wallet-identity/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/social-walletlink-wallet-identity/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/social-walletlink-wallet-identity/api-mcp