MCP tool ·
read
2 credits
thornode_tx_get
Fetch a single THORChain transaction by hash. Tries GET /thorchain/tx/{hash} first (native THORChain types); falls back to GET /cosmos/tx/v1beta1/txs/{hash} for Wasm/contract transactions.
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_tx_get",
"arguments": {
"hash": "<hash>"
}
}
}
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
hash
|
string | required | 64-char hex tx hash. |
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.
Look up THORChain tx ABCDEF1234567890ABCDEF1234567890ABCDEF1234567890ABCDEF1234567890.
Get the full payload for the tx with hash 0123...EF — including events.
Resolve THORChain transaction abc123def456...e0 — was it a swap or a wasm call?
Example response
Illustrative shape — actual values vary.
response shape
{
"observed_tx": {
"tx": {
"id": "ABCDEF1234567890...",
"chain": "THOR",
"from_address": "thor1abc...xyz",
"to_address": "thor1xyz...abc",
"coins": [
{
"asset": "THOR.RUNE",
"amount": "12000000000"
}
]
},
"block_height": "19543210",
"status": "done"
}
}
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).