INSTALLABLE · LOCAL · PRE-RELEASENot independently reviewed. See what you can use today for every surface
side by side.
node on your PATH; there is no WalletWall account, backend or
GitHub App involved.
Install
The public repository acts as its own plugin marketplace. WalletWall is not listed in a GitHub or
Copilot catalog and is not published to npm.
Try it
Ask in a new session:walletwall-resolve_asset and a PARTIAL result: the address matches WalletWall’s registry, but
no issuer attestation was presented, so identity is not ESTABLISHED.
To exercise the visual surface:
What the plugin contains
The four skills
The skills are methodology, not evidence. Among other rules, they tell the model to report evidence
states rather than truth, surface limitations and conflicts, keep
NO_RESULT distinct from zero, treat
symbols as non-identity, and never ask for private keys, seed phrases or signatures.
Vault technical readiness is evidence-only.
assess_vault_readiness asks whether the presented
asset-identity and balance evidence satisfies WalletWall’s published readiness criteria. It does not
configure, authorize or execute a vault.The WalletWall canvas
The canvas (walletwall-evidence-explorer) renders The Wall: sources, observations, assertions,
WalletWall derivations and the readiness keystone as a deterministic graph, with the selected claim’s
support, authority, freshness, finality, conflicts, limitations and provenance beside it.
- It computes no evidence state. Evidence states come from the same bundled server used by the MCP tools; the WallPrint view displays engine results serialized into the plugin.
- Colour never signals safety. Terracotta marks focus and attention, never good or bad.
- Addresses are shown in full, with chain ID and a Copy control.
- The agent drives the canvas with
open_canvasand the actionsset_bundle,select_assertionandget_view.
Canvas inputs and bundled fixtures
Canvas inputs and bundled fixtures
The canvas accepts a WWEP bundle plus
evaluatedAt, a bundled evidence fixture, a bundled WallPrint
fixture, or a portable WallPrint reference. Evidence fixtures include usdc-established,
stale-identity, conflicting-balances, partial-provider-balance, unknown-balance,
superseded-balance and readiness-blocked. The WallPrint view includes synthetic corrected,
superseded, withdrawn, replay and receipt scenarios.How it connects
The plugin declares one local stdio server:walletwall-resolve_asset; all eleven resources are available over MCP.
Trust boundary
- WalletWall-controlled code does not retain MCP query history or send query data to WalletWall infrastructure.
- GitHub Copilot and its model provider see every prompt, tool input and tool output under their own policies.
- The canvas listener is loopback-only and separate from the MCP server.
- No GitHub App, token or OAuth credential is passed to WalletWall MCP.
Compatibility and verification notes
Compatibility and verification notes
The CLI path above was verified with Copilot CLI 1.0.103: add marketplace, install, list plugin, list
MCP server and uninstall all succeeded. An earlier plugin build was also loaded in the Windows Copilot
app with its tools, skill, server and canvas. The current app install click-through, resource listing,
first-tool-call prompt behavior and side-panel rendering have not all been re-verified on the current
plugin build. UI labels may change; the CLI commands above are the verified installation path.
Uninstall
Understand the evidence model
Learn what the states and limitations mean before relying on them.
Review privacy & security
See exactly what Copilot, the model provider and WalletWall-controlled code can access.

