Categories › Data & Databases › Files, spreadsheets, CSV & PDFs
Read-only QIE chain data: balances, tx status, tokens, network facts. Chains 1990 and 1983. No keys.
Remote server: your requests and data go to mcp.qie.digital. Claude Code: claude mcp add --transport http qie-wallet https://mcp.qie.digital/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
qie_get_balances — Read the native QIE balance and known token balances for an address on QIE mainnet (chain 1990) or testnet (chain 1983). Pass a checksummed qie_resolve_name — Resolve a QIE ID such as yourname.qie to its QIE address on QIE mainnet (chain 1990). A bare label gets .qie appended. The server reads the qie_reverse_lookup — Look up the QIE ID, such as yourname.qie, for an address on QIE mainnet (chain 1990): the default QIE ID the owner chose, otherwise the freeqie_get_tx_status — Read whether a transaction is pending, successful, failed, or not found on QIE mainnet (chain 1990) or testnet (chain 1983). The result inclqie_list_tokens — List tokens on QIE mainnet (chain 1990) or testnet (chain 1983). Official tokens come from the curated list and are marked source config, ofqie_get_network_info — Return the pinned facts for QIE mainnet (chain 1990) or testnet (chain 1983): chain ID, name, RPC URLs, explorer URL, and native currency. ENot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.