thorchain_secured_asset_get · 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": "thorchain_secured_asset_get",
    "arguments": {
      "asset": "<asset>",
      "slug": "<slug>"
    }
  }
}

Arguments

Name	Type	Required	Description
`asset`	string	optional
`slug`	string	optional

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.

Get the BTC-BTC secured asset on THORChain.

Look up the secured asset with slug "btc-btc".

How much depth does the ETH-ETH secured asset have?

Example response

Illustrative shape — actual values vary.

response shape

{
  "asset": "BTC-BTC",
  "slug": "btc-btc",
  "friendly_name": "BTC",
  "depth": "12.34567890",
  "supply": "12.34567890",
  "canonical_asset": {
    "slug": "bitcoin",
    "symbol": "BTC",
    "name": "Bitcoin"
  },
  "denom": {
    "slug": "btc-btc",
    "base": "btc-btc",
    "symbol": "BTC",
    "network": {
      "slug": "mainnet-thorchain",
      "name": "THORChain",
      "thorchain_symbol": "THOR"
    }
  },
  "last_sync_at": "2026-05-04T08:00:00Z"
}

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.