walletlink.social MCP server
online · 100% uptimesocial.walletlink/wallet-identity·v1.4.0·1 starsResolve wallet addresses to X and Farcaster accounts, and back again.
1 stars
Reviews
Write oneNobody has reviewed walletlink.social yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
walletlink.social tools (8, 1 write)
write = sends, deletes, buys or postswalletlink_account_balanceFreeHow 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. unmetered is true on an account that is never debited. Its matches_available is null because it has no balance to report, not because the balance is zero.
walletlink_estimate_listFreeA 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.
walletlink_index_coverageFreeHow 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_job_statusFreeProgress 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.
walletlink_resolve_walletsFreeResolve 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.
walletlink_submit_jobwrite actionFreeSubmit 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.
walletlink_wallets_by_farcaster_usernameFreeFind 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 still shows it, labeled. Needs a key that belongs to an account: a key bought with USDC alone gets ACCOUNT_REQUIRED. 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.
walletlink_wallets_by_x_handleFreeFind 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; resolving that address still shows it, labeled. Needs a key that belongs to an account: a key bought with USDC alone gets ACCOUNT_REQUIRED. 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.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 733ms20/20
- Tool poisoning8 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
How walletlink.social compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 8
- the typical server has 7
- Tools that change things
- 13%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 218 ms
- faster than 61% of 30,031 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
What its tools let an agent do: 7 read · 1 change
Release history: 2 versions in the registry since 2026-09-16, latest 2026-09-21, typically one every 5 days.
Install walletlink.social in Claude Code, Cursor or VS Code
claude mcp add --transport http wallet-identity https://walletlink.social/api/mcp
What the publisher says
From the walletlink.social repository's README, as published. We do not edit it. Read it on GitHub
walletlink.social
Turn wallet addresses into the people behind them, and reach them where they already are
App · Docs · API · @walletlinkETH
How it works
Wallet list in (CSV · contract address · paste)
├─ Resolve against a 4.85M-wallet identity index
├─ Farcaster: complete protocol coverage, refreshed daily
├─ X handles: attested first, labeled always, never inferred
├─ Rank by holdings × follower reach
└─ Export CSV, or an X list ready to importIt also runs backwards: give it an X handle or a Farcaster username and it returns the wallets attached to that person.
Coverage, stated honestly
The number most tools quote is the one that flatters them. Two numbers matter here, and conflating them will make you plan a campaign you cannot run.
The chain decides this more than the collection does: Base sits at the top of that range because Base is where Farcaster lives, Ethereum near the bottom. The measured per-chain table lives in the coverage docs. Use your chain’s figure, not an average.
Having an account and reaching it are different claims. Of 473,215 X handles resolved, 70.1% are live, 20.1% suspended and 9.8% are names nobody holds. Matches carry that answer wherever the handle has been resolved.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
walletlink.social: common questions
- Is walletlink.social MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the walletlink.social safety report
- How do I install walletlink.social?
- It runs remotely at walletlink.social. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does walletlink.social need an API key?
- Yes. The registry entry asks for
Authorization. - Is walletlink.social maintained?
- The last commit was 33 days ago (2026-10-02). The latest release is v1.4.0.
- Is walletlink.social up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does walletlink.social compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.