Claude BlockchainQuery connectorWhat Claude can do in your BlockchainQuery account.
The Claude BlockchainQuery connector exposes 37 tools. 36 read public blockchain data, 0 write anything, and 1 is described too vaguely to classify. Below: what Claude can look up across more than 60 networks, what the desktop extension sends out, and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can query blockchains directly
Checking a wallet usually means finding the right explorer for each chain, pasting the address, and repeating the routine on the next network. BlockchainQuery, a no-cost extension from the Pocket Network Foundation, lets you ask Claude instead: it queries the chain through Pocket Network's public gateway and answers in plain words, with no account and no API key.
One question, several chains. compare_balances sets the native balance of an address side by side on several networks, and resolve_domain turns an ENS name into the address to query first.
Follow a transaction to the end. On EVM chains, evm_get_transaction and evm_get_receipt together show who sent what, the gas used and whether it succeeded; Solana, Cosmos, Sui, Near and Radix have their own lookups.
Read staking and governance. cosmos_get_staking breaks down delegations and pending rewards, and cosmos_get_governance brings up proposals and votes.
What it will not do: no documented tool signs or broadcasts a transaction, and none needs your wallet. Nothing watches an address on its own either: Claude queries only while it answers, and the extension itself runs on your own machine, in Claude Desktop. One tool, a raw EVM call, is described too briefly to say more. The Integrations hub lists the other families on this site.
Five words to know
The Claude vocabulary of this page, explained once.
- Connector
- A link you set once between Claude and an outside service or program, so Claude can call on it while it answers.
- Tool
- One named action a connector offers. Claude decides on its own which ones to call, and the directory sheet lists each by name.
- Authorization
- The service's own screen where you grant Claude access. BlockchainQuery needs none, since it reads public data without signing in.
- Approval
- The confirmation Claude waits for before an action that changes an account, shown in the chat at the point it matters.
- MCP
- The shared standard behind connectors: it lets an assistant like Claude work with an outside program such as BlockchainQuery.
Set up the Claude BlockchainQuery connector
- 01
Find BlockchainQuery
Open Claude's settings, then Customize and Connectors, and look for BlockchainQuery. On a Team or Enterprise workspace, an Owner or Primary Owner enables a connector for the organization before members can use it.
- 02
Start the connection
Click Connect on its row and follow the window that appears. If the link breaks later, choose Disconnect and connect again; that is how Claude expects a damaged connection to be repaired.
- 03
Read any authorization
If an authorization screen appears, read it before accepting: it belongs to the service, not to Claude, and it defines what access Claude gets. BlockchainQuery says it requires no authentication at all.
The 37 tools, by family
BlockchainQuery gives Claude 37 tools: 36 that read your account, 0 that change something in it, and 1 no official source describes.
Pocket Network's README describes all 37 tools in one line each. 36 clearly read; one is too vague to classify. Names stay as Claude shows them.
- 36 read
- 1 not documented
What Claude reads (36)
36 toolsDiscovery, EVM, Solana, Cosmos, Sui, Near, Radix and cross-chain lookups, all on public data.
list_chains
Returns the networks BlockchainQuery currently supports, optionally narrowed to one protocol family or to one network, so Claude knows where a question can be answered.
get_chain_info
Gives the profile of one chain: its RPC address, protocol type, the methods it supports and its current status.
evm_get_balance
Looks up how much of the native coin an address holds on any EVM-compatible chain, such as ETH on Ethereum, Arbitrum or Base.
evm_get_block
Pulls up a block on an EVM chain, by number or by hash, with the details the node returns for it, such as its timestamp and its transactions.
evm_get_transaction
Brings back one transaction from an EVM chain by its hash: with the details recorded on chain for it.
evm_get_receipt
Retrieves the receipt of a transaction, which is where success or failure, gas used and emitted logs are recorded.
evm_get_logs
Searches event logs on an EVM chain within a block range, so Claude can find, for example, transfers emitted by one contract.
evm_estimate_gas
Estimates the gas a transaction would cost on an EVM chain, giving a figure before anything is signed elsewhere.
evm_get_token_info
Reads an ERC-20 token's name, symbol, decimals and total supply, along with the token balance of an address.
evm_call_contract
Runs a read-only call to a smart contract function on an EVM chain and returns the answer, without any transaction.
solana_get_balance
Checks the SOL balance of a Solana address, or its balance in an SPL token, in a single lookup.
solana_get_account
Shows the information Solana stores about an account, which helps Claude tell what kind of account an address is.
solana_get_block
Pulls the details of a Solana block from its slot number, with what the network recorded for that slot.
solana_get_transaction
Finds a Solana transaction from its signature and returns what was recorded for it.
solana_get_signatures
Lists the recent transaction signatures linked to a Solana address, the starting point for reviewing its activity.
cosmos_get_balance
Reads either the native balance or every token balance of an address on a Cosmos SDK chain such as Osmosis or Akash.
cosmos_get_staking
Shows the staking delegations of an address and the rewards attached to them, as recorded on the Cosmos chain you ask about.
cosmos_get_validators
Returns the validator set of a Cosmos chain, or the details of a single validator.
cosmos_get_transaction
Looks up a transaction on a Cosmos SDK chain by its hash and returns its recorded details.
cosmos_get_governance
Brings up governance proposals on a Cosmos chain and the votes cast on them.
cosmos_get_block
Returns a Cosmos block, either at a given height or the most recent one, so Claude can tell whether the chain is still producing blocks.
sui_get_balance
Gives the SUI balance of an address, or its balance in another token on Sui.
sui_get_object
Describes a Sui object from its ID; on Sui, assets and many other things live as objects.
sui_get_transaction
Retrieves a Sui transaction from its digest, the identifier Sui gives each transaction, along with the details recorded for it.
sui_get_coins
Lists coin details for an address on Sui, page by page when there are many.
near_query
Answers questions about a Near account: its info, view function calls, access keys or contract state, depending on what Claude asks. One tool thus serves several kinds of Near request.
near_get_block
Brings back a Near block by height or hash, or simply the latest one, with what the network recorded for it.
near_get_transaction
Gives the status of a Near transaction together with its receipts, which is where Near records what each step produced.
radix_get_network_status
Reports the state of the Radix network: state version, epoch, round and timestamp.
radix_get_network_config
Shows the Radix network configuration, including version information and the well-known addresses that apps on the network rely on.
radix_get_balance
Lists all the fungible token balances held by a Radix account address, so the whole account is visible in one answer.
radix_get_transaction_status
Checks the status of a Radix transaction from its intent hash, the identifier Radix uses for a submitted transaction.
radix_get_consensus_manager
Reads the state of the Radix consensus manager, which includes the current validator set and the epoch information.
resolve_domain
Translates an ENS or Unstoppable Domains name into the blockchain address it points to.
compare_balances
Puts native token balances of an address side by side across several chains in one go.
convert_units
Converts amounts between blockchain denomination units, such as raw on-chain integers and human-readable values.
Not classified (1)
1 toolA tool whose one-line description does not say whether it only reads. Its effect is left unstated here.
evm_call
Pocket Network's README describes this tool in one line, as executing a JSON-RPC call on any EVM chain, without saying whether that only reads or can also alter anything. No source settles it, so its effect is not stated here; the general approval rule further down applies.
What Claude asks before acting
By default, Claude stops and asks for confirmation before each action it carries out on an account for someone, in the conversation.
Here 36 tools read public data and none is described with a prompt of its own; the raw EVM call is covered by the same general rule. On Team and Enterprise workspaces, owners decide whether members may let some actions through without a prompt each time, and they can cap what any connector may do for the whole organization; nobody overrides that from their own account. Pocket Network adds that the extension runs on your machine and sends queries straight to its public gateway.
Which plans include BlockchainQuery
No official source publishes plan availability connector by connector: 0 of the 819 directory sheets shows it, and the gap is real.
The published rule is general. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions like this one install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members connect. The connector's sheet in the official directory shows its current state. Only Pocket Network documents this connector; no Claude help page covers it.
Where BlockchainQuery stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing alerts you when a balance moves or a proposal opens.
By default, the sheet exposes only reading among the classified tools, an observed floor rather than a guarantee: an administrator can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic writes on every sheet that it neither chooses a publisher's tools nor guarantees their behavior. Install what comes from a publisher you trust. For a connector that works inside a business account, see the Claude agility-cms connector.
Need help connecting BlockchainQuery to Claude?
A person reads every message.