thornode_node_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": "thornode_node_get",
    "arguments": {
      "address": "<address>"
    }
  }
}

Arguments

Name	Type	Required	Description
`address`	string	required	THORNode validator address (thor1...).

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 validator info for THORNode thor1abc...xyz.

Is the node thor1...xyz currently active or standby?

How much bond does THORNode validator thor1abc...xyz have?

Example response

Illustrative shape — actual values vary.

response shape

{
  "node_address": "thor1abc...xyz",
  "status": "Active",
  "pub_key_set": {
    "secp256k1": "thorpub1..."
  },
  "validator_cons_pub_key": "thorcpub1...",
  "bond": "1000000000000",
  "active_block_height": "19200000",
  "forced_to_leave": false,
  "leave_height": "0",
  "ip_address": "198.51.100.1",
  "version": "1.131.0"
}

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.
UPSTREAM: Returned when the upstream HTTP call fails (relayer tools only).