putty
MCPPrivyWallets

privy_get_wallet_by_address

Resolve an on-chain address to a Privy wallet. Hits `POST /v1/wallets/address` with `{ address, chain_type }`. Returns a single `PrivyWallet` on a hit, a 404 on a miss. The handler does the same ownership check as `privy_get_wallet`: a wallet whose `owner_id` is `null` or does not match the caller's DID returns a 403-style isError. Use this when you have an address and need to confirm the wallet exists in Putty and is owned by the caller; for the inverse direction (a wallet id and the address), use `privy_get_wallet`.

Resolve an on-chain address to a Privy wallet. Hits POST /v1/wallets/address with { address, chain_type }. Returns a single PrivyWallet on a hit, a 404 on a miss.

Endpoint

POST /v1/wallets/address

Input

The tool takes a single JSON object. Every field, its type, and an example are on the generated reference at GET /mcp/tools, under this tool's name.

Calling it

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": { "name": "privy_get_wallet_by_address", "arguments": {} }
}

Put your arguments in place of the empty object. A call that fails comes back as a normal result carrying isError: true and a message naming what went wrong, not as a JSON-RPC protocol error.

Notes

The handler does the same ownership check as privy_get_wallet: a wallet whose owner_id is null or does not match the caller's DID returns a 403-style isError. Use this when you have an address and need to confirm the wallet exists in Putty and is owned by the caller; for the inverse direction (a wallet id and the address), use privy_get_wallet.

The full request and response shape, and a live playground, live on the generated reference at GET /mcp/tools.

On this page