QED tools, in plain words.

Choose the question you need answered, then open a real example. QED reads public chain data; it does not recommend trades.

Start with a question

Tool	Question it answers	One-click example
Guard	Is this token what it claims to be, and what can its issuer do to it?	Open a Guard result
Check	Does this pool use the issuer's published contract?	Review a real NVDA pool with Guard
Powers	What can the issuer do to this token?	Browse NVDA's observed controls
Statement	What did these wallets hold, provably?	Create a wallet statement
Registry	Which contracts did each issuer publish?	Browse NVDA registry entries
Verify	Is this QED record genuine and still fresh?	Browse signed records to re-check

Pool: a contract where two tokens are traded against each other. Registry: the list of contract addresses each issuer has published.

Three two-minute paths

AI agent: connect MCP

In Claude Code, run:

claude mcp add --transport http qed https://qed.web3-energy.com/mcp

Claude Desktop and Cursor can use this HTTP server config:

{
  "mcpServers": {
    "qed": {
      "type": "http",
      "url": "https://qed.web3-energy.com/mcp"
    }
  }
}

Try asking: Before I swap, check whether NVDA on Ethereum matches its issuer’s published contract and report any observed token controls. Do not call it safe.

App: call the API

Send a pool address to Guard for an issuer match and observed controls:

curl --request POST https://qed.web3-energy.com/api/guard \
  --header 'Content-Type: application/json' \
  --data '{"address":"0xeE6F200063a53Fe9450578d99c0F8eAD4952c97a","chain":"ethereum"}'

See the API reference for response fields and the distinction between unknown and mismatch.

Auditor: keep a Statement

Create a Statement for the wallet and chain.
Download the resulting JSON record.
POST that JSON to /verify to check its signature and freshness.

See API reference → Verify for the request and response shape.