QIE Wallet is listed as active in the registry but did not answer our last check. It exposes 6 tools.
Read-only QIE chain data: balances, tx status, tokens, network facts. Chains 1990 and 1983. No keys.
Uptime history
5 days of history · worst day 0%
5 days agonow
0.0%
Uptime 24h
0 of 92 checks
6
Tools
read from the server
98 ms
Response time
average over 24h
open, no key
Access
streamable-http
QIE Wallet does not always answer
Over the last week it answered 13.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.
run in your terminal
claude mcp add wallet --transport http https://mcp.qie.digital/mcpSettings → Connectors → Add custom connector, then paste this address
https://mcp.qie.digital/mcp~/.codex/config.toml
[mcp_servers.wallet]
url = "https://mcp.qie.digital/mcp".cursor/mcp.json
{
"mcpServers": {
"wallet": {
"url": "https://mcp.qie.digital/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"wallet": {
"type": "http",
"url": "https://mcp.qie.digital/mcp"
}
}
}Available tools 6
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
qie
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 or all-lowercase hex address. A QIE ID such as yourname.qie is accepted on mainnet and is resolved the same way as qie_resolve_name; if it does not resolve, the status is unresolved and no balance is invented. Amounts are raw integers plus a decimal formatting of those integers. This tool does not give price, APY, returns, yield, or investment advice and will decline such questions.
qie_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. Example QIE ID: yourname.qie. The caller cannot supply an RPC URL or chain ID. This tool does not give price, APY, returns, yield, or investment advice and will decline such questions.
qie_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 includes the block number, confirmations, from, to, value, token transfers when the explorer reports them, and an explorer link. Example QIE ID: yourname.qie. This does not submit a transaction. This tool does not give price, APY, returns, yield, or investment advice and will decline such questions.
qie_list_tokens
List tokens on QIE mainnet (chain 1990) or testnet (chain 1983) from the configured token list or the network explorer. An optional query matches symbol or name. yourname.qie is a QIE ID example, not a token query. Results are capped at 50 and do not include prices. This tool does not give price, APY, returns, yield, or investment advice and will decline such questions.
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 ID record stores (free QIE IDs first, then paid) whose source is published on the QIE explorer, and checks that each upgradeable proxy still points at the reviewed implementation. A name with no record returns status ok with address null. The address always comes from the chain. When the server has the QIE ID API configured, the result can also include otherChainAddresses (bitcoin, solana, tron, xrp records), each one only if the record store holds the same value on chain. QIE ID is not deployed on testnet (chain 1983), so lookups there return status unresolved. No address is guessed. This tool does not give price, APY, returns, yield, or investment advice and will decline such questions.
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 free QIE ID the address holds. When the chain gives no name and the server has the QIE ID API configured, the names the API lists for the address are tried, free QIE IDs first. A name is shown only when it resolves back to the same address through a QIE ID record store published on the QIE explorer. An address with no QIE ID returns status ok with name null. QIE ID is not deployed on testnet (chain 1983), so lookups there return status unresolved. No name is guessed. This tool does not give price, APY, returns, yield, or investment advice and will decline such questions.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.qie.digital/mcp | streamable-http | answering | 98 ms | 5 min ago |
Alternatives to QIE Wallet
same job, measured the same wayBase Intel MCP
by datakoot
Read-only on-chain intel for AI agents on Base: balances, tokens, gas, tx status. No API keys.
Wallet and token data on 5 EVM chains
by cyberpunk11147
Wallet balances, token prices, gas, decoded transactions and ENS on 5 EVM chains. No RPC key.
Base Intel MCP
by datakoot
Read-only on-chain intelligence for AI agents on Base: balances, tokens, gas, tx status.
Fuse Network
by fuse
MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.
Ankr Agent RPC
by w3tech
Read chain data on 200+ networks and Sui: transactions, logs, balances, objects, ABI-decoded.
Cortexcloud
by jonahthan433
Pay-per-call on-chain data for AI agents: token, wallet, risk, whale, NFT, tx. No API keys.
THORChain Swap
by thorchain-swap
Read-only THORChain swap quotes, liquidity pools, and network status.
Etherscan
by etherscan
Read-only Etherscan V2 blockchain data: balances, transactions, transfers, tokens, contracts, logs.
QIE Wallet — questions
Answers built from our own checks of this server.
What can QIE Wallet do?
It exposes 6 tools, read directly from the server on our last check. Among them: qie_get_balances, qie_get_network_info, qie_get_tx_status, qie_list_tokens, qie_resolve_name, qie_reverse_lookup. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is QIE Wallet working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 98 ms. The bar chart above shows every period we have measured.
The registry lists QIE Wallet as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect QIE Wallet?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does QIE Wallet need an API key?
No. QIE Wallet completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.