walletlink.social MCP server
social.walletlink/wallet-identitywalletlink.socialstreamable-httpv1.4.0Scanned
Resolve wallet addresses to X and Farcaster accounts, and back again.
8 tools: 6 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the walletlink.social MCP server can do
The walletlink.social MCP server is published by walletlink.social, a domain the MCP Registry verified. It has 8 tools. It can create or change data (6 tools: walletlink_resolve_wallets, walletlink_wallets_by_x_handle, walletlink_wallets_by_farcaster_username, walletlink_index_coverage and 2 more), but cannot delete data. 2 tools only read.
1 tool brings in text other people can write (walletlink_submit_job).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 6Claude Code: ask
walletlink_account_balanceHow many match credits the configured key has left, and how much of the request allowance it has used.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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. 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.
Annotations the server declares
- title: Match credit balance
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
walletlink_index_coverageHow much of the index carries each identity type.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Index coverage
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
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.1 finding
Why it is in this group
- The name "walletlink_resolve_wallets" says "resolve": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "walletlink_resolve_wallets" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "walletlink_resolve_wallets" says "resolve": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Resolve wallets to social identities
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
walletlink_submit_jobSubmit a list of addresses as a background job.Reads text others writeNo findings
Why it is in this group
- The name "walletlink_submit_job" says "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Submit a background lookup job
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
walletlink_wallets_by_farcaster_usernameFind the wallets in the index attested to a Farcaster account.1 finding
Why it is in this group
- The description's first verb is "find": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "walletlink_wallets_by_farcaster_username" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "find": a word for reading.
Description, as the server wrote it 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 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.
Annotations the server declares
- title: Find wallets behind a Farcaster username
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
walletlink_wallets_by_x_handleFind the wallets in the index attested to an X account.No findings
Why it is in this group
- The name "walletlink_wallets_by_x_handle" says "handle": a word for a change.
Description, as the server wrote it 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; 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.
Annotations the server declares
- title: Find wallets behind an X handle
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 2Show 2 read-only tools
walletlink_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.No findings
Why it is in this group
- The name "walletlink_estimate_list" says "list": a word for reading.
Description, as the server wrote 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.
Annotations the server declares
- title: Estimate a list before spending on it
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
walletlink_job_statusProgress and results for a job submitted with walletlink_submit_job.No findings
Why it is in this group
- The name "walletlink_job_status" says "status": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a background job
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:19 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://walletlink.social/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://walletlink.social
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://walletlink.social/api/mcp: tools/list returned 8 tools to an anonymous client, including walletlink_resolve_wallets (write), walletlink_wallets_by_x_handle (write), walletlink_wallets_by_farcaster_username (write), walletlink_index_coverage (write), walletlink_account_balance (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "walletlink_resolve_wallets" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "walletlink_resolve_wallets" says "resolve": a word for reading.
The server marks "walletlink_wallets_by_farcaster_username" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "find": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http wallet-identity https://walletlink.social/api/mcpclaude mcp add --transport http wallet-identity https://walletlink.social/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__wallet-identity__walletlink_job_status",
"mcp__wallet-identity__walletlink_estimate_list"
],
"ask": [
"mcp__wallet-identity__walletlink_resolve_wallets",
"mcp__wallet-identity__walletlink_wallets_by_x_handle",
"mcp__wallet-identity__walletlink_wallets_by_farcaster_username",
"mcp__wallet-identity__walletlink_index_coverage",
"mcp__wallet-identity__walletlink_account_balance",
"mcp__wallet-identity__walletlink_submit_job"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wallet-identity. Review it before you use it.
Capability tags behind 1 rule
- mcp__wallet-identity__walletlink_submit_job untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/social.walletlink/wallet-identity/verify?hash=ba5f7b0671e24646196369ce6b3670619c2d9484502e60190a620f6ffce8b189" | jq -e '.changed == false'Pinned hash ba5f7b0671e2, from Nov 18, 2026, 08:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/social.walletlink/wallet-identity/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/social.walletlink/wallet-identity)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.
walletlink.social MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the walletlink.social MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the walletlink.social MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the walletlink.social MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the walletlink.social MCP server have?
- 8 tools: 6 write, 2 read. walletlink_resolve_wallets, walletlink_wallets_by_x_handle, walletlink_wallets_by_farcaster_username, walletlink_index_coverage, walletlink_account_balance, walletlink_submit_job, walletlink_job_status and walletlink_estimate_list.
Does the walletlink.social MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the walletlink.social MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the walletlink.social MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.