GUIDE

Use QED with an LLM

Connect an AI agent to QED’s issuer-match tools over MCP.

QED exposes a stateless, read-only MCP server at https://qed.web3-energy.com/mcp. The server card describes its tools.

In Claude Code, connect with:

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

For ChatGPT, Cursor, and other MCP clients, add an HTTP MCP server in your client’s MCP settings using https://qed.web3-energy.com/mcp. Product labels and availability vary by client.

Tools:

  • qed_check compares a pool or token with its issuer registry entry.
  • qed_guard signs a read-only review of issuer identity, observed powers, source status, known pools, and optional wallet restrictions.
  • qed_powers reports observed token control signals for registry contracts.
  • qed_wallet checks known registry-token holdings for a wallet.
  • qed_statement signs selected wallets’ observed registry-token balances.
  • qed_registry_lookup finds issuer contracts by ticker.
  • qed_verify verifies a signed QED document.

Try asking:

  • “Is this pool the real NVDA token?”
  • “What can the issuer do to this token?”
  • “Sign a statement of what these wallets hold”

QED does not prove backing, custody, reserves, solvency, safety, price, liquidity, or endorsement.

QED's read-only MCP check flow An agent asks QED to check NVDA, QED reads the chain through RPC, and returns a signed match. LLM Is this the real NVDA? MCP · /mcp QED issuer match Chain RPC read-only Match, signed