INSTALLABLE · LOCAL · PRE-RELEASENot independently reviewed. See what you can use today for every surface
side by side.
0.1.0, WWEP 0.1, eleven resources).
Before you start
Clone the source repository and check your Node.js version (22.18 or newer):plugin/server/walletwall-mcp.mjs. It imports only Node.js
built-ins, so no npm install is needed. Steps 1 and 2 use a POSIX shell (macOS, Linux, WSL or Git
Bash); step 3 runs anywhere Node.js does.
1. Ask one question, with no AI client
MCP over stdio is newline-delimited JSON-RPC, so you can pipe messages straight into the server: aninitialize request, the initialized notification, then one tool call. The server answers each
request on its own line and exits when its input ends.
resolve_asset result. Its structuredContent, abridged:
PARTIAL. A registry match is
WalletWall’s own lookup (WALLETWALL_DERIVED), and no issuer attestation was presented with this
query, so the asset’s identity is not ESTABLISHED. The registry itself was verified once, against
Circle’s publication on 2026-10-24, and says nothing about later changes.
2. Normalize a reading
Suppose your own tooling read a balance at a finalized block.normalize_observation turns that draft
into a canonical WWEP observation. It does not fetch anything: you supply the reading. The block, hash,
holder and amount below are synthetic.
canonicalJson, the RFC 8785 serialization that was
hashed):
- The token address was lowercased; every quantity stays a string.
evidenceDigestcovers the whole observation;contentDigestcovers onlyresult,subjectandpayload, so two readings of the same thing share it whatever their IDs, sources and times.balanceDecimalis exact:1500000atomic units at 6 decimals is1.5, computed with integers and never rounded.- Had the reading come back empty (
"result": "NO_RESULT", no balance fields), the payload would be{}andbalanceDecimalwould benull. No result is never zero.
3. Evaluate a bundle and assess readiness
An evidence bundle gathers sources, observations and the assertions they support. The engine publishes complete synthetic bundles as resources, each with the exact tool call to make. This short script reads one and makes that call. Save it asquickstart.mjs in the walletwall-copilot
directory:
quickstart.mjs
vault-readiness-established, holds two assertions: an asset identity attested by
the issuer’s publication, and a balance read from chain state at a finalized block. The resource’s tool
call is assess_vault_readiness. Result, abridged:
TRANSPORT_FIDELITY_NOT_VERIFIED: the engine cannot check that a chain reading was faithfully retrieved. It evaluates evidence as presented.WALLETWALL_DERIVED_NOT_UPSTREAM_AUTHORITY: the classification is WalletWall’s rule applied to the inputs. It is not a statement by the issuer or the chain.doesNotEstablishlists what technical readiness never implies.
inspect_evidence:
ESTABLISHED, with freshness PINNED (it is about a specific block),
finality FINALIZED, and authority canonical-chain-state satisfied.
4. Watch it fail closed
Now replay the example in which the asset’s identity was only read from chain state and no issuer attestation exists:NOT_ESTABLISHED: not “not ready”, and
not a guess. The example resource also names the smallest measurement that could change the outcome:
An AUTHORITY_ATTESTED observation of the identity from an ISSUER_PUBLICATION source whose authorityId equals the registry authorityId for the deployment.
5. Try it from your AI client
Once the server is connected to your client (Install & Connect), ask in plain language. For example:Next steps
Tools
Inputs, outputs and refusals for all six tools.
Evidence Model (WWEP)
Why the same evidence can be ESTABLISHED, STALE or PARTIAL.

