> ## Documentation Index
> Fetch the complete documentation index at: https://docs.walletwall.org/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub Copilot

> Install the WalletWall plugin in GitHub Copilot, use its local MCP server and four skills, and understand the WalletWall canvas and trust boundary.

> [!NOTE]
>
> **INSTALLABLE · LOCAL · PRE-RELEASE**
>
> Not independently reviewed. See [what you can use today](https://docs.walletwall.org/concepts/product-status.md) for every surface
> side by side.

The WalletWall plugin brings the local WalletWall MCP server, four guidance skills and the WalletWall
canvas into GitHub Copilot. It needs `node` on your `PATH`; there is no WalletWall account, backend or
GitHub App involved.

## Install

```bash theme={null}
copilot plugin marketplace add Wallet-Wall/walletwall-copilot
copilot plugin install walletwall@walletwall
```

The verified CLI installation reports:

```text theme={null}
Plugin "walletwall" installed successfully. Installed 4 skills.
```

Start a **new** Copilot session after installing. Then verify the plugin and MCP server:

```bash theme={null}
copilot plugin list --json
copilot mcp list
```

> [!NOTE]
>
> 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:

```text theme={null}
Is 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on chain 1 definitely canonical USDC?
```

Expect `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:

```text theme={null}
Show the stale-identity fixture in the WalletWall canvas.
```

The canvas should show the stale identity and its limitations without converting the state into a
"safe" or "verified" badge.

## What the plugin contains

| Part | What it does |
| - | - |
| **WalletWall MCP** | Local stdio server with all six tools and eleven resources |
| **Four skills** | Guide tool selection and interpretation without creating evidence or overriding results |
| **WalletWall canvas** | Shows one evidence bundle or one WallPrint disclosure from the engine output |

### The four skills

| Skill | Focus |
| - | - |
| `walletwall-evidence` | General evidence interpretation and tool selection |
| `walletwall-evidence-audit` | Claim decomposition, conflicts, limitations and the next missing measurement |
| `walletwall-authority` | Authority, provenance, transport, independence and derivation |
| `vault-readiness` | Technical-readiness criteria, blockers and fail-closed summaries |

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.

> [!NOTE]
>
> **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_canvas` and the actions `set_bundle`, `select_assertion` and
  `get_view`.

> [accordion] 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:

```json theme={null}
{
  "mcpServers": {
    "walletwall": {
      "type": "stdio",
      "command": "node",
      "args": ["${PLUGIN_ROOT}/server/walletwall-mcp.mjs"]
    }
  }
}
```

Copilot starts it with no URL and no environment. The six tools appear with the server name as a
prefix, such as `walletwall-resolve_asset`; all eleven resources are available over MCP.

## Trust boundary

```mermaid theme={null}
flowchart LR
    accTitle: Trust boundary of the WalletWall plugin in GitHub Copilot
    accDescr: The user talks to GitHub Copilot, which exchanges prompts and tool data with the model provider. On the user's machine, Copilot starts the WalletWall MCP server over stdio and the WalletWall canvas extension, which serves its page on a loopback-only listener and starts the bundled server for each request. Neither WalletWall component contacts any remote service.

    user["You"]
    copilot["GitHub Copilot<br/>CLI or app"]
    model["Model provider"]
    subgraph machine["Your machine"]
        mcp["WalletWall MCP<br/>stdio, no network, no writes"]
        canvas["WalletWall canvas<br/>loopback-only listener"]
    end

    user --> copilot
    copilot <-->|"prompts and tool data"| model
    copilot -->|"stdio"| mcp
    copilot --> canvas
    canvas -->|"stdio, per request"| mcp

    class user input;
    class copilot,model external;
    class mcp process;
    class canvas security;

    classDef input fill:#FAF8F3,stroke:#C9A47A,color:#1E1A14,stroke-width:1.5px;
    classDef process fill:#BF4E32,stroke:#8B3120,color:#FAF8F3,stroke-width:1.5px;
    classDef decision fill:#C9A47A,stroke:#8B6F47,color:#1E1A14,stroke-width:1.5px;
    classDef output fill:#E6DED2,stroke:#9A9186,color:#1E1A14,stroke-width:1.5px;
    classDef risk fill:#8B3120,stroke:#1E1A14,color:#FAF8F3,stroke-width:1.5px;
    classDef datastore fill:#1E1A14,stroke:#9A9186,color:#FAF8F3,stroke-width:1.5px;
    classDef external fill:#FAF8F3,stroke:#9A9186,color:#1E1A14,stroke-width:1.5px;
    classDef security fill:#1E1A14,stroke:#C9A47A,color:#FAF8F3,stroke-width:1.5px;
```

* 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.

> [accordion] 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

```bash theme={null}
copilot plugin uninstall walletwall
copilot plugin marketplace remove walletwall
```

> [card] [Understand the evidence model](https://docs.walletwall.org/mcp/evidence-model.md)
>
> Learn what the states and limitations mean before relying on them.

> [card] [Review privacy & security](https://docs.walletwall.org/mcp/privacy-security.md)
>
> See exactly what Copilot, the model provider and WalletWall-controlled code can access.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.