QIE Wallet MCP server
digital.qie/walletqie.digitalstreamable-httpv0.1.0Scanned
Read-only QIE chain data: balances, tx status, tokens, network facts. Chains 1990 and 1983. No keys.
6 tools: 6 only read.
- Reads private data · 0
- Reads text others write · 6
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the QIE Wallet MCP server can do
The QIE Wallet MCP server is published by qie.digital, a domain the MCP Registry verified. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
6 tools bring in text other people can write (qie_get_balances, qie_resolve_name, qie_reverse_lookup and 3 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Only reads 6Show 6 read-only tools
qie_get_balancesRead the native QIE balance and known token balances for an address on QIE mainnet (chain 1990) or testnet (chain 1983).Reads text others writeNo findings
Why it is in this group
- The name "qie_get_balances" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
qie_get_network_infoReturn the pinned facts for QIE mainnet (chain 1990) or testnet (chain 1983): chain ID, name, RPC URLs, explorer URL, and native currency.Reads text others writeNo findings
Why it is in this group
- The name "qie_get_network_info" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
qie_get_tx_statusRead whether a transaction is pending, successful, failed, or not found on QIE mainnet (chain 1990) or testnet (chain 1983).Reads text others writeNo findings
Why it is in this group
- The name "qie_get_tx_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
qie_list_tokensList tokens on QIE mainnet (chain 1990) or testnet (chain 1983).Reads text others writeNo findings
Why it is in this group
- The name "qie_list_tokens" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List tokens on QIE mainnet (chain 1990) or testnet (chain 1983). Official tokens come from the curated list and are marked source config, official, and verified, with chain name and chainId on every curated row. Explorer tokens may follow and are not official. The same address is official WETH on QIE and official WQIE on Ethereum; results are keyed by chainId and address, and that collision is noted on the token. A known unofficial Wrapped QIE and a known unofficial WETH on QIE are marked not official and not verified. 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
qie_resolve_nameResolve a QIE ID such as yourname.qie to its QIE address on QIE mainnet (chain 1990).Reads text others writeNo findings
Why it is in this group
- The name "qie_resolve_name" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
qie_reverse_lookupLook 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.Reads text others writeNo findings
Why it is in this group
- The name "qie_reverse_lookup" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:qie_get_balancesOnly readsdescriptioninputSchema
- Changed:qie_list_tokensOnly readsdescription
- Changed:qie_resolve_nameOnly readsdescription
- Changed:qie_reverse_lookupOnly readsdescription
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http wallet https://mcp.qie.digital/mcpclaude mcp add --transport http wallet https://mcp.qie.digital/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__wallet__qie_get_balances",
"mcp__wallet__qie_resolve_name",
"mcp__wallet__qie_reverse_lookup",
"mcp__wallet__qie_get_tx_status",
"mcp__wallet__qie_list_tokens",
"mcp__wallet__qie_get_network_info"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wallet. Review it before you use it.
Capability tags behind 6 rules
- mcp__wallet__qie_get_balances untrusted-input
- mcp__wallet__qie_resolve_name untrusted-input
- mcp__wallet__qie_reverse_lookup untrusted-input
- mcp__wallet__qie_get_tx_status untrusted-input
- mcp__wallet__qie_list_tokens untrusted-input
- mcp__wallet__qie_get_network_info untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/digital.qie/wallet/verify?hash=2b8a7f605a5143479402e8d3786fb52b06ecd1ecc934c3e555692b541c2688f1" | jq -e '.changed == false'Pinned hash 2b8a7f605a51, from Nov 16, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/digital.qie/wallet/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/digital.qie/wallet)Source: MCP Registry. Synced Nov 3, 2026, 11:17 UTC.
QIE Wallet MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the QIE Wallet MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the QIE Wallet MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the QIE Wallet MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the QIE Wallet MCP server have?
- 6 tools: 6 read. qie_get_balances, qie_resolve_name, qie_reverse_lookup, qie_get_tx_status, qie_list_tokens and qie_get_network_info.
Does the QIE Wallet MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the QIE Wallet MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the QIE Wallet MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.