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

# MCP Resources

> The eleven static resources WalletWall MCP serves about itself: schemas, policies, registry data, versions and synthetic examples.

A **tool** computes over input you send. A **resource** is static information bundled into the server.
WalletWall MCP exposes exactly **eleven resources** so a client can understand its contract without
reading the source repository.

> [card] Build valid evidence
>
> Schemas, claim contracts, authority policies and the WWEP draft.

> [card] Understand the bundled world
>
> Stablecoin deployments, chain metadata and the versions actually running.

> [card] Learn by example
>
> Four complete synthetic inputs with the exact tool calls and expected outcomes.

## Tools vs resources

| | Tool | Resource |
| - | - | - |
| What it is | A function that computes over input you send | A static document bundled into the server |
| How you use it | `tools/call` with arguments | `resources/read` with a `walletwall://` URI |
| Result depends on | Your input and, where relevant, `evaluatedAt` | Only the server build you run |
| Examples | `inspect_evidence`, `assess_vault_readiness` | `walletwall://schemas/claims`, `walletwall://policies/authority` |

The resource set is fixed when the server is built. There are no resource templates, subscriptions or
prompts, and nothing is loaded remotely. Each resource's SHA-256 is pinned in
`security/tool-manifest.json`.

## The eleven resources

### Build valid evidence

| URI | What it contains |
| - | - |
| `walletwall://schemas/evidence` | JSON Schema for a WWEP 0.1 evidence bundle |
| `walletwall://schemas/claims` | Per-claim subject, value, observation-linkage and authority contract |
| `walletwall://policies/authority` | Claim-specific authority policies |
| `walletwall://spec/wwep` | WalletWall Evidence Profile 0.1 draft text |

### Understand the bundled world

| URI | What it contains |
| - | - |
| `walletwall://registry/stablecoins` | Five bundled stablecoin deployments and their point-in-time verification |
| `walletwall://registry/chains` | The three bundled chains and their finality models |
| `walletwall://conformance/version` | Versions and content digests of the registry, policies, rules and specification |

### Learn by example

| URI | Expected outcome |
| - | - |
| `walletwall://examples/identity-established` | `inspect_evidence`: identity `ESTABLISHED` |
| `walletwall://examples/balance-established` | `inspect_evidence`: balance `ESTABLISHED`, `PINNED`, `FINALIZED` |
| `walletwall://examples/vault-readiness-established` | `assess_vault_readiness`: `CRITERIA_MET` |
| `walletwall://examples/vault-readiness-not-established` | `assess_vault_readiness`: `NOT_ESTABLISHED`, with the missing measurement named |

> [!NOTE]
>
> All four examples are synthetic. Their shape may be reused; their evidence may not. Never present an
> example as evidence about a real wallet, balance or chain state.

## Contract and specification

> [accordion] walletwall://schemas/evidence
>
> The bundle schema accepted by `inspect_evidence`, `check_invariants`, `trace_provenance` and
> `assess_vault_readiness`: `wwepVersion` (`"0.1"`), sources, observations, assertions, derivations,
> and optional conflicts, supersessions, registry version and rules version. Bundle records are
> closed; a claim's `subject` and `value` and an observation's `payload` are bounded open maps.

> [accordion] walletwall://schemas/claims
>
> The per-claim contract generated from the bundled policies and evaluator rules: required subject and
> value keys, accepted origins and source kinds, observation linkage, registry/derivation relationships
> and the diagnostics attached to shape failures.

> [accordion] walletwall://policies/authority
>
> The authority rules for the five claim types. Authority is defined per claim type; there is no
> global ranking of source kinds. See [Evidence Model (WWEP)](https://docs.walletwall.org/mcp/evidence-model.md).

> [accordion] walletwall://spec/wwep
>
> The WalletWall-defined WWEP 0.1 draft: data model, states, invariants, canonicalization, evaluation
> procedure and known limitations. It is not an industry standard.

## Reference data

`walletwall://registry/stablecoins` contains five deployments, each verified once against an issuer or
protocol publication and a finalized `decimals()` reading on 2026-10-24.

| Asset | Chain (ID) | Contract | Decimals | `authorityId` |
| - | - | - | - | - |
| USDC | Ethereum (`1`) | `0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48` | 6 | `issuer:circle` |
| USDC | Base (`8453`) | `0x833589fcd6edb6e08f4c7c32d4f71b54bda02913` | 6 | `issuer:circle` |
| USDC | Arbitrum One (`42161`) | `0xaf88d065e77c8cc2239327c5edb3a432268e5831` | 6 | `issuer:circle` |
| USDT | Ethereum (`1`) | `0xdac17f958d2ee523a2206206994597c13d831ec7` | 6 | `issuer:tether` |
| DAI | Ethereum (`1`) | `0x6b175474e89094c44da98b954eedeac495271d0f` | 18 | `protocol:sky` |

`walletwall://registry/chains` contains Ethereum Mainnet, Base and Arbitrum One with a descriptive
finality model for each. The engine does not independently verify finality; it evaluates the finality
each observation declares.

> [!WARNING]
>
> The registry is a point-in-time snapshot, not live chain data. Registry-derived results carry
> `REGISTRY_VERIFIED_POINT_IN_TIME`; the snapshot says nothing about later contract changes, safety or
> solvency.

## Versions and digests

Read `walletwall://conformance/version` when you need to know what the running server actually contains.
At the time of writing it reports:

```json theme={null}
{
  "status": "DRAFT_PRIVATE_PRE_RELEASE",
  "wwepVersion": "0.1",
  "engineVersion": "0.1.0",
  "registryVersion": "0.2.0",
  "registryStatus": "VERIFIED_POINT_IN_TIME",
  "registrySha256": "ee59e7940b0b66aa0fa33b81dfb353f2dd5347cbaeba758e0d65183289a8da87",
  "policiesVersion": "0.1.0-draft",
  "policiesSha256": "0457e5a8272d3443766b24852b1752baf38ec13e766ea6e5fd88cafefde7f3ce",
  "rulesVersion": "0.1.0-draft",
  "rules": [
    { "ruleId": "wwdr.usd-value", "rulesVersion": "0.1.0-draft" },
    { "ruleId": "wwvr.vault-technical-readiness", "rulesVersion": "0.1.0-draft" }
  ],
  "specSha256": "d3eec0c4e9a5ab907b936c1713d097009e22003d83b599abef9d776eb5d5910a"
}
```

`status` is the engine's own pre-release label. These digests identify the registry, policies and
specification used for a result; the resource does not carry a digest of the engine bundle itself.

## Recommended workflow

**1. Read the claim contract**

Start with `walletwall://schemas/claims` and the synthetic example closest to the claim you need.

**2. Assemble your own evidence**

Reuse the example's shape, not its evidence. Your measurements remain your inputs.

**3. Inspect before deriving readiness**

Call `inspect_evidence`. If the result contains shape diagnostics, fix the bundle and treat the
corrected bundle as new input.

**4. Assess vault readiness only when it applies**

`assess_vault_readiness` is an evidence-only classification over the required identity and balance
assertions. It does not configure, authorize or execute a vault.

## Unknown resource URIs

URIs are exact strings. Reading anything outside the eleven listed above returns a JSON-RPC error with
`Unknown resource.` Asking for resource templates or prompts returns `Method not found`, because the
server offers neither.

> [card] [Understand WWEP](https://docs.walletwall.org/mcp/evidence-model.md)
>
> See how the resources become evidence states and assessments.

> [card] [See WallPrint](https://docs.walletwall.org/mcp/wallprint.md)
>
> Learn how a completed assessment can become a deliberately published disclosure.


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