Home / MCP registry index / org.thorchain/thorchain-mcp
THORChain MCP
org.thorchain/thorchain-mcp in the official MCP registry.
Endpoint https://mcp.thorchain.org/mcp. Source: gitlab.com/thorchain/thorchain-mcp.
The registry describes it as: Read-only THORChain data: pools, network, nodes, vaults, transactions, Midgard history.
We read its 126 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
check_reference_memo get_affiliate_earnings get_affiliate_history get_affiliate_stats get_ban get_block get_bonds get_churns get_cometbft_block get_cometbft_block_results get_cometbft_consensus_params get_cometbft_consensus_state get_cometbft_net_info get_cometbft_status get_cometbft_tx get_cometbft_validators get_constants get_cosmos_account get_cosmos_balances get_cosmos_block get_cosmos_delegations get_cosmos_latest_block get_cosmos_node_info get_cosmos_rewards get_cosmos_supply get_cosmos_syncing get_cosmos_tx get_cosmos_validators get_depth_history get_derived_pool get_dynamic_l1_fees get_earnings_history get_holders get_inbound_addresses get_invariant get_keygen get_keygen_metric get_keysign get_keysign_pubkey get_known_pools get_lastblock get_lastblock_chain get_limit_swaps get_limit_swaps_summary get_liquidity_history get_lp_position get_members get_midgard_balance get_midgard_member get_midgard_nodes get_midgard_stats get_mimir get_mimir_admin get_mimir_key get_mimir_node get_network_info get_network_summary get_node get_oracle_price get_oracle_prices and 66 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/org-thorchain-thorchain-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.