Skip to content

MCP servers › org.thorchain › thorchain-mcp

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

org.thorchain/thorchain-mcp

Read-only THORChain data: pools, network, nodes, vaults, transactions, Midgard history. — the publisher's description

1 of 1 record check metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedversion 1.0.0streamable HTTP126 tools

Summary

org.thorchain/thorchain-mcp is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 126 tools, 0 resources and 0 prompts.

Record checks

1 of 1 record check met · 7 do not apply · 1 not checked

  • met: Registry entry is active and says how to run it
  • not checked: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Tools
126
Described as changing data
0 of 126 toolsAI-classified
Mainly works on
nothing outside itself: it only answers questionsAI-classified
Topic
finance-and-paymentsAI-classified
Last tested
2026-10-23

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-10-21 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-21 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-21).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
126tools
0resources
0prompts

What it mainly works on, as our AI model read its tool descriptions: nothing outside itself: it only answers questions.

None of its 126 tools are described as changing anything. For 6 the reading was uncertain, so no mark is shown.

  • check_reference_memoreads or searches

    “Pre-flight check for memoless transactions.”

    Publisher declares: read-only yes · idempotent no

    2 inputs, 2 required
    • assetstringrequired“The asset (e.g.”
    • amountstringrequired“The transaction amount in base units”
  • get_affiliate_earningsreads or searches

    “Returns affiliate earnings including fees collected by thorname.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_affiliate_historyreads or searches

    “Returns historical affiliate swap data including volumes and thorname breakdown over time.”

    Publisher declares: read-only yes · idempotent no

    4 inputs
    • intervalstring“Time interval: 5min hour day week month quarter year”
    • frominteger“Start timestamp (Unix seconds)”
    • tointeger“End timestamp (Unix seconds)”
    • countinteger“Number of intervals to return”
  • get_affiliate_statsreads or searches

    “Returns affiliate statistics including volumes, counts, and fees by thorname.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_banon 1 other serverreads or searches

    “Returns the ban status for a node address.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“The node address to check ban status for (thor1...)”
  • get_blockon 23 other serversreads or searches

    “Returns verbose details of a THORChain block including header info, transactions, and block events.”

    Publisher declares: read-only yes · idempotent no

    1 input
    • heightnull or integer“Optional block height.”
  • get_bondsreads or searches

    “Returns bond details for an address including associated nodes and total bonded amount.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“Address to get bond details for”
  • get_churnsreads or searches

    “Returns churn event history with dates and block heights.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_cometbft_blockreads or searches

    “Returns block data at the specified height including header, transactions, and commit signatures.”

    Publisher declares: read-only yes · idempotent no

    1 input
    • heightinteger“Block height to query.”
  • get_cometbft_block_resultsreads or searches

    “Returns the results of executing transactions in a block, including ABCI events and validator updates.”

    Publisher declares: read-only yes · idempotent no

    1 input
    • heightinteger“Block height to query.”
  • get_cometbft_consensus_paramsreads or searches

    “Returns CometBFT consensus parameters (block size, evidence, validator params) at a height.”

    Publisher declares: read-only yes · idempotent no

    1 input
    • heightinteger“Block height (0 or omitted for latest)”
  • get_cometbft_consensus_statereads or searches

    “Returns the current consensus round state including height/round/step, proposal block hash, and vote information.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

Show 88 more tools
  • get_cometbft_net_inforeads or searches

    “Returns network information including listening status, connected peers, and peer details.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_cometbft_statusreads or searches

    “Returns the CometBFT node status including node info, sync status, and validator information.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_cometbft_txreads or searches

    “Returns a transaction by its hash including tx result, height, and optional proof of inclusion.”

    Publisher declares: read-only yes · idempotent no

    2 inputs, 1 required
    • hashstringrequired“Transaction hash (without 0x prefix).”
    • proveboolean“Include proof of transaction inclusion.”
  • get_cometbft_validatorsreads or searches

    “Returns the validator set at the specified height including addresses, public keys, and voting power.”

    Publisher declares: read-only yes · idempotent no

    3 inputs
    • heightinteger“Block height to query.”
    • pageinteger“Page number for pagination (1-indexed).”
    • per_pageinteger“Number of validators per page.”
  • get_constantsreads or searches

    “Returns protocol constants including integer, boolean, and string configuration values that govern THORChain behavior.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_cosmos_accountreads or searches

    “Returns account information for a THORChain address including account number, sequence (nonce), and public key if available.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“THORChain address (thor1...)”
  • get_cosmos_balancesreads or searches

    “Returns account balances for a THORChain address.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“THORChain address (thor1...)”
  • get_cosmos_blockreads or searches

    “Returns a block at the specified height from the Cosmos SDK blockchain including header, transactions, and commit data.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • heightintegerrequired“Block height to query”
  • get_cosmos_delegationsreads or searches

    “Returns all delegations for a delegator address.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • delegator_addrstringrequired“Delegator address (thor1...)”
  • get_cosmos_latest_blockreads or searches

    “Returns the latest block from the Cosmos SDK blockchain including header, transactions, and commit data.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_cosmos_node_inforeads or searches

    “Returns Cosmos SDK node information including network, version, protocol versions, and application version.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_cosmos_rewardsreads or searches

    “Returns delegation rewards for a delegator address.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • delegator_addrstringrequired“Delegator address (thor1...)”
  • get_cosmos_supplyreads or searches

    “Returns the total token supply including all coin denominations.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_cosmos_syncingreads or searches

    “Returns whether the node is currently syncing with the blockchain.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_cosmos_txreads or searches

    “Returns a transaction by hash from the Cosmos SDK blockchain.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • hashstringrequired“Transaction hash”
  • get_cosmos_validatorsreads or searches

    “Returns the list of staking validators.”

    Publisher declares: read-only yes · idempotent no

    1 input
    • statusstring“Filter by validator status: BOND_STATUS_BONDED, BOND_STATUS_UNBONDING, or BOND_STATUS_UNBONDED.”
  • get_depth_historyreads or searches

    “Returns historical depth data for a pool including asset depth, RUNE depth, asset price, and liquidity units over time intervals.”

    Publisher declares: read-only yes · idempotent no

    5 inputs, 1 required
    • assetstringrequired“Pool asset identifier (e.g.”
    • intervalstring“Time interval: 5min hour day week month quarter year”
    • frominteger“Start timestamp (Unix seconds)”
    • tointeger“End timestamp (Unix seconds)”
    • countinteger“Number of intervals to return”
  • get_derived_poolreads or searches

    “Returns one derived (virtual) pool's depths and status.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • assetstringrequired“The derived asset (e.g.”
  • get_dynamic_l1_feesreads or searches

    “Returns per-THORName dynamic L1 minimum swap-fee floors (ADR-026).”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_earnings_historyon 3 other serversreads or searches

    “Returns historical earnings data including liquidity fees, block rewards, and bonding/liquidity earnings over time intervals.”

    Publisher declares: read-only yes · idempotent no

    4 inputs
    • intervalstring“Time interval: 5min hour day week month quarter year”
    • frominteger“Start timestamp (Unix seconds)”
    • tointeger“End timestamp (Unix seconds)”
    • countinteger“Number of intervals to return”
  • get_holderson 5 other serversreads or searches

    “Returns top RUNE holders with their balances.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_inbound_addressesreads or searches

    “Returns vault addresses for depositing assets into THORChain.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_invariantreads or searches

    “Runs a specific protocol invariant check and returns the result.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • invariantstringrequired“The invariant name to check (e.g.”
  • get_keygenreads or searches

    “Returns keygen information for a specific block height and pubkey.”

    Publisher declares: read-only yes · idempotent no

    2 inputs, 2 required
    • heightintegerrequired“The block height of the keygen ceremony”
    • pubkeystringrequired“The pubkey of one of the keygen block members”
  • get_keygen_metricreads or searches

    “Returns keygen timing metrics for a specific vault public key.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • pubkeystringrequired“The vault public key (thorpub...)”
  • get_keysignreads or searches

    “Returns keysign information for a specific block height.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • heightintegerrequired“The block height to get keysign information for”
  • get_keysign_pubkeyreads or searches

    “Returns keysign information for a specific block height and vault pubkey.”

    Publisher declares: read-only yes · idempotent no

    2 inputs, 2 required
    • heightintegerrequired“The block height to get keysign information for”
    • pubkeystringrequired“The vault pubkey to filter keysign information”
  • get_known_poolsreads or searches

    “Returns known pools with their status (available, staged, suspended).”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_lastblockreads or searches

    “Returns the last observed and signed block heights for all chains.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_lastblock_chainreads or searches

    “Returns the last observed and signed block heights for a specific chain.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • chainstringrequired“The chain to get last block for (e.g.”
  • get_limit_swapsreads or searches

    “Returns the limit swaps queue containing pending limit orders.”

    Publisher declares: read-only yes · idempotent no

    7 inputs
    • offsetinteger“Number of items to skip (default: 0)”
    • limitinteger“Number of items to return (default: 100, max: 1000)”
    • source_assetstring“Filter by source asset (e.g.”
    • target_assetstring“Filter by target asset (e.g.”
    • senderstring“Filter by sender address”
    • sort_bystring“Sort field: ratio, age, amount, or created_height (default: ratio)”
    • sort_orderstring“Sort order: asc or desc (default: asc)”
  • get_limit_swaps_summaryreads or searches

    “Returns a summary of the limit swaps queue including total count, total USD value, breakdown by asset pair, oldest swap age, and average age.”

    Publisher declares: read-only yes · idempotent no

    2 inputs
    • source_assetstring“Filter by source asset (e.g.”
    • target_assetstring“Filter by target asset (e.g.”
  • get_liquidity_historyon 1 other serverreads or searches

    “Returns historical liquidity change data including add/withdraw counts, volumes, and net liquidity over time intervals.”

    Publisher declares: read-only yes · idempotent no

    4 inputs
    • intervalstring“Time interval: 5min hour day week month quarter year”
    • frominteger“Start timestamp (Unix seconds)”
    • tointeger“End timestamp (Unix seconds)”
    • countinteger“Number of intervals to return”
  • get_lp_positionreads or searches

    “Returns liquidity provider position information for a specific address in a pool.”

    Publisher declares: read-only yes · idempotent no

    2 inputs, 2 required
    • assetstringrequired“The pool asset (e.g.”
    • addressstringrequired“The LP address to lookup”
  • get_memberson 1 other serverreads or searches

    “Returns list of all liquidity provider addresses.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_midgard_balancereads or searches

    “Returns balance for an address from Midgard analytics.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“Address to get balance for”
  • get_midgard_memberreads or searches

    “Returns liquidity provider positions for an address including pool participation, units, and deposit/withdraw history.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“THORChain address (thor1...) or external chain address”
  • get_midgard_nodesreads or searches

    “Returns node information including addresses and public keys from Midgard analytics.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_midgard_statsreads or searches

    “Returns global network statistics including swap counts, volumes, liquidity metrics, and RUNE price.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_mimirreads or searches

    “Returns THORChain protocol configuration parameters (Mimir values).”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_mimir_adminreads or searches

    “Returns the admin mimir configuration.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_mimir_keyreads or searches

    “Returns the effective value for a specific mimir key.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • keystringrequired“The mimir key to look up (e.g.”
  • get_mimir_nodereads or searches

    “Returns the mimir settings voted by a specific node.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“The node address to get mimir votes for (thor1...)”
  • get_network_infoon 4 other serversreads or searches

    “Returns THORChain network statistics and health information including bond metrics, pool data, and node counts.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_network_summaryon 2 other serversreads or searches

    “Compact THORChain network status for agents: node counts, bonding/liquidity APY, reserve, pooled RUNE, next churn height, vault migration flag.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_nodeon 17 other serversreads or searches

    “Returns detailed information for a specific validator node including bond, status, version, and performance metrics.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“The node address (thor1...)”
  • get_oracle_priceon 1 other serverreads or searches

    “Returns the oracle price for a specific asset symbol.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • symbolstringrequired“The asset symbol to get the price for (e.g.”
  • get_oracle_pricesreads or searches

    “Returns all oracle prices for supported assets.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_outbound_fee_assetreads or searches

    “Returns outbound fee information for a specific asset including the fee amount, surplus/deficit tracking, and dynamic multiplier.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • assetstringrequired“The asset to get outbound fee for (e.g.”
  • get_outbound_feesreads or searches

    “Returns outbound fee information for all assets including the fee amount, surplus/deficit tracking, and dynamic multiplier.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_outbound_queuereads or searches

    “Returns the outbound queue containing signed transactions waiting to be broadcast to external chains.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_poolon 7 other serversreads or searches

    “Returns detailed information for a specific liquidity pool by asset identifier.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • assetstringrequired“The asset identifier (e.g.”
  • get_pool_slipreads or searches

    “Returns slip data for one pool, including current slip and rollup statistics.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • assetstringrequired“The pool asset (e.g.”
  • get_pool_statson 3 other serversreads or searches

    “Returns detailed analytics and statistics for a specific liquidity pool including volume, fees, APY, and historical metrics.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • assetstringrequired“The asset identifier (e.g.”
  • get_queueon 4 other serversreads or searches

    “Returns queue statistics including pending swap count, outbound transaction count, internal queue size, and scheduled outbound value.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_ragnarokreads or searches

    “Returns whether the chain is in Ragnarok (emergency shutdown mode).”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_reference_memoreads or searches

    “Returns the memoless transaction memo for a given asset and reference number.”

    Publisher declares: read-only yes · idempotent no

    2 inputs, 2 required
    • assetstringrequired“The asset (e.g.”
    • referencestringrequired“The reference number”
  • get_reference_memo_by_hashreads or searches

    “Returns the memoless transaction memo for a given reference hash.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • hashstringrequired“The transaction hash”
  • get_rune_historyreads or searches

    “Returns historical RUNE data including price over time intervals.”

    Publisher declares: read-only yes · idempotent no

    4 inputs
    • intervalstring“Time interval: 5min hour day week month quarter year”
    • frominteger“Start timestamp (Unix seconds)”
    • tointeger“End timestamp (Unix seconds)”
    • countinteger“Number of intervals to return”
  • get_rune_poolreads or searches

    “Returns the RUNEPool state: protocol-owned liquidity, provider shares, reserve position, deposit limits, and pending deposits/withdrawals.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_rune_price_historyreads or searches

    “Returns historical RUNE price data in USD over time intervals.”

    Publisher declares: read-only yes · idempotent no

    4 inputs
    • intervalstring“Time interval: 5min hour day week month quarter year”
    • frominteger“Start timestamp (Unix seconds)”
    • tointeger“End timestamp (Unix seconds)”
    • countinteger“Number of intervals to return”
  • get_rune_providerreads or searches

    “Returns one RUNEPool provider's position: deposited RUNE, units, and PnL.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“The provider's THORChain address (thor1...)”
  • get_runepool_memberreads or searches

    “Returns Midgard's analytics view of a RUNEPool member: deposit/withdraw history and current units.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“The member's THORChain address (thor1...)”
  • get_scheduled_queuereads or searches

    “Returns the scheduled outbound queue containing transactions waiting to be signed and broadcast.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_stable_reservereads or searches

    “Returns the Stable Reserve module status: RUNE balance, depeg tolerance, POL share, per-asset inventory with health flags and oracle prices, and active deployment swaps.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_stable_reserve_contributorreads or searches

    “Returns a contributor's Stable Reserve credit for a given stable asset and address.”

    Publisher declares: read-only yes · idempotent no

    2 inputs, 2 required
    • assetstringrequired“The stable asset (e.g.”
    • addressstringrequired“The contributor's L1 address”
  • get_streaming_swapreads or searches

    “Returns details of a specific streaming swap by transaction hash, including progress (count/quantity), amounts swapped (in/out), and any failed sub-swaps.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • hashstringrequired“The inbound transaction hash of the streaming swap”
  • get_swap_detailsreads or searches

    “Returns detailed information about a specific swap including its current state.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • tx_idstringrequired“The transaction ID of the swap to look up”
  • get_swap_historyreads or searches

    “Returns historical swap data including swap counts, volumes, fees, and average slip over time intervals.”

    Publisher declares: read-only yes · idempotent no

    4 inputs
    • intervalstring“Time interval: 5min hour day week month quarter year”
    • frominteger“Start timestamp (Unix seconds)”
    • tointeger“End timestamp (Unix seconds)”
    • countinteger“Number of intervals to return”
  • get_swap_queuereads or searches

    “Returns the current swap queue containing pending swaps waiting to be executed.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_swapper_cloutreads or searches

    “Returns an address's swapper clout: accumulated fee-based score that reduces outbound delays for trusted swappers.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“The swapper's address (any chain)”
  • get_tcy_claimerreads or searches

    “Returns TCY (ThorCoin Yeet) claimer information for a specific address.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“The THORChain address to get TCY claimer info for (thor1...)”
  • get_tcy_distributionreads or searches

    “Returns TCY distribution for an address.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“Address to get TCY distribution for”
  • get_tcy_stakerreads or searches

    “Returns TCY (ThorCoin Yeet) staker information for a specific address.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“The THORChain address to get TCY staker info for (thor1...)”
  • get_thornamereads or searches

    “Returns THORName registration information including owner, expiry, and registered chain addresses.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • namestringrequired“The THORName to lookup (e.g.”
  • get_thorname_ownerreads or searches

    “Returns THORNames owned by an address.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“Owner address to get THORNames for”
  • get_trade_accountreads or searches

    “Returns all trade account positions for a specific address.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • addressstringrequired“The address to lookup trade accounts for”
  • get_trade_unitreads or searches

    “Returns trade unit information for a specific asset.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • assetstringrequired“The trade asset to lookup (e.g.”
  • get_tss_metricsreads or searches

    “Returns TSS keygen and keysign timing metrics across the validator set.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

  • get_tvl_historyreads or searches

    “Returns historical Total Value Locked (TVL) data including pooled value, bonded value, and total locked value over time intervals.”

    Publisher declares: read-only yes · idempotent no

    4 inputs
    • intervalstring“Time interval: 5min hour day week month quarter year”
    • frominteger“Start timestamp (Unix seconds)”
    • tointeger“End timestamp (Unix seconds)”
    • countinteger“Number of intervals to return”
  • get_txon 1 other serverreads or searches

    “Returns transaction details for a given hash including observed transaction data, status, and processing stages.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • hashstringrequired“The transaction hash (inbound or outbound)”
  • get_tx_detailsreads or searches

    “Returns comprehensive transaction details including observed transactions, actions taken, outbound transactions, consensus and finalized heights, and whether the vault was updated or the transaction …”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • hashstringrequired“The transaction hash (inbound or outbound) to get detailed information for”
  • get_tx_stagesreads or searches

    “Returns detailed processing stages of an inbound transaction including observation counts, confirmation status, swap status (with streaming progress if applicable), outbound delay, and signing status.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • hashstringrequired“The inbound transaction hash to check processing stages for”
  • get_tx_statuson 1 other serverreads or searches

    “Returns comprehensive transaction status including processing stages, planned outbound transactions, and completed outbound transactions.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • hashstringrequired“The inbound transaction hash to check status for”
  • get_upgrade_proposalreads or searches

    “Returns a specific upgrade proposal by name including target block height and upgrade information.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • namestringrequired“The upgrade proposal name (e.g.”
  • get_upgrade_votesreads or searches

    “Returns all node votes for a specific upgrade proposal.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • namestringrequired“The upgrade proposal name to get votes for (e.g.”
  • get_vaulton 4 other serversreads or searches

    “Returns a specific vault by its public key including coin balances, status, membership, routers, and chain addresses.”

    Publisher declares: read-only yes · idempotent no

    1 input, 1 required
    • pubkeystringrequired“The vault public key (thorpub1...)”
  • get_vault_pubkeysreads or searches

    “Returns all vault public keys organized by type: Asgard (active network vaults), Yggdrasil (node vaults), and inactive vaults.”

    Publisher declares: read-only yes · idempotent no

    Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. The first 100 of 126 tools are listed. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 120 tools
Says what it returns
100% of 120 tools
States limits, defaults or errors
6% of 116 tools
Says when to use it
44% of 57 tools
Items covered per tool
2.8 of 4 on average

Counted from the listing

Parameters with a description
100% of 151
Tools with a description
100% of 126
Typical description length
148 characters

The tool set

Counted from the listing

Tools
126
Size of the list
about 13,904 tokens for an agent to load (characters ÷ 4)
Naming
125 of 126 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 120 of 126 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.thorchain.org/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "thorchain-mcp": {
      "url": "https://mcp.thorchain.org/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "thorchain-mcp": {
      "type": "http",
      "url": "https://mcp.thorchain.org/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"thorchain-mcp","type":"http","url":"https://mcp.thorchain.org/mcp"}'
Claude Code
claude mcp add --transport http thorchain-mcp https://mcp.thorchain.org/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.thorchain.org/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.thorchain.org/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
org.thorchain
Repository
gitlab.com/thorchain/thorchain-mcp

Source: the registry entry and api.github.com · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

1 of 1 record check met · 7 do not apply · 1 not checked

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not checkedSource repository link opensThe link is not on GitHub; we only open GitHub repositories.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about org.thorchain/thorchain-mcp

Answered from the data above

Does org.thorchain/thorchain-mcp need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has org.thorchain/thorchain-mcp been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

What can org.thorchain/thorchain-mcp do?

It lists 126 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search. We did not call any tool, so this describes the text, not the behaviour.

Can org.thorchain/thorchain-mcp change or delete data?

None of its 126 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,665 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 126 tools, 0 resources, 0 prompts.
  4. 6,323 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
does not apply
no existing GitHub repository (repository is hosted on gitlab, not GitHub, so this layer does not apply)
Hosting type
registry · 2026-10-23
MCP capability
logging, tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
repository is hosted on gitlab, not GitHub, so this layer does not apply
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “org.thorchain/thorchain-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/org.thorchain/thorchain-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 1 record check met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/org.thorchain/thorchain-mcp)](https://protocolprobe.com/mcp/servers/org.thorchain/thorchain-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology