wallet_list · MCP API Docs

JSON-RPC call

Paste this body into your MCP client's `tools/call` request. The `id` field is the JSON-RPC message correlator (caller-chosen, not a record identifier — set it to anything; the server echoes it back).

tools/call body

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "wallet_list",
    "arguments": {
      "state": "<state>",
      "limit": 1
    }
  }
}

Arguments

Name	Type	Required	Description
`state`	string	optional	Filter by Wallet#state. Default: any state except `draft`.
`limit`	integer	optional	Page size (default 100, max 200).

Copy-paste prompt samples

Drop one of these into Claude Code, n8n, or any MCP client. Your AI agent should pick this tool to answer.

Which wallets support hardware signing for THORChain?

List every wallet available on iPhone.

Show me the published browser wallets in the deving.zone catalogue.

What wallets work on both Linux and Android?

Example response

Illustrative shape — actual values vary.

response shape

{
  "wallets": [
    {
      "slug": "leap",
      "name": "Leap",
      "description": "Cosmos-native browser + mobile wallet.",
      "state": "published",
      "capabilities": {
        "browser": true,
        "hardware": false,
        "instant": true,
        "keystore": true,
        "mac": true,
        "windows": true,
        "linux": true,
        "mobile_android": true,
        "mobile_iphone": true
      }
    }
  ]
}

Possible errors

VALIDATION: Returned when the arguments fail the typed schema.
NOT_FOUND: Returned when the requested resource does not exist in our DB.
RATE_LIMIT: Returned when your token's credit budget is exhausted.