Finance · Remote MCP server
walletlink.social
Resolve wallet addresses to X and Farcaster accounts, and back again.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
social.walletlink/wallet-identity- Version
- 1.4.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-09-21
- Updated
- 2026-09-21
- Publisher
- social.walletlink
- Namespace
- Namespace verified by the MCP Registry via the domain walletlink.social · how
- Website
- docs.walletlink.social/mcp-server
- Repository
- github.com/starl3xx/wallet-to-social
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://walletlink.social/api/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- walletlink.social 1.4.1 · protocol 2025-06-18
- Tools discovered
- Not listed - timeout: no answer within 15 s
- Checked on
- 2026-10-05
How to connect walletlink.social
walletlink.social is a remote MCP server: there is nothing to install. Its endpoint is https://walletlink.social/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| WalletapIssue and manage Apple Wallet & Google Wallet passes from any AI assistant. | Local · stdio |
| walletbureau.comRisk score for a Base wallet before your agent pays it: 0-100, verdict and explained flags. | Local · stdio |
| Walletconnect MCPNon-custodial EVM wallet bridge over WalletConnect: balances, signing, transactions. | Local · stdio |
| WalletlensEVM wallet reports and Robinhood Stock Token intelligence paid with USDC over x402. | Local · stdio |
| WalletTriageReal-time exploit-exposure risk check for EVM wallets, paid per query via x402 (USDC on Base). | Local · stdio |
| WalletWallet: Apple and Google Wallet passesCreate, update, and revoke Apple Wallet and Google Wallet passes from any MCP client. | Remote · HTTPLive check: sign-in required |
| WarmContext and automation MCP server for Warm financial data and approved write operations. | Local · stdio |
| WarpSIP trunking, numbers, porting, messaging, billing, and CDR analytics on the Ringer WARP platform. | Local · stdio |