Skip to main content
INSTALLABLE · LOCAL · PRE-RELEASENot independently reviewed. See what you can use today for every surface side by side.
WalletWall MCP is a local stdio server. Your MCP client starts it as a child process and exchanges JSON-RPC messages over standard input and output. There is no WalletWall account, API key or hosted MCP service to configure.

Requirements

  • Node.js 22.18 or newer, available as node on your PATH.
  • Git, when you install from a repository clone.
  • No WalletWall account, credential or hosted service.

Choose your client

Add the WalletWall repository as a plugin marketplace, then install the plugin:
Start a new session afterwards. The plugin bundles the local server, four skills and the WalletWall canvas. See GitHub Copilot for the full integration guide.

Verify the connection

A current WalletWall MCP connection should have all three of these properties:
1

Six tools

Your client lists exactly resolve_asset, normalize_observation, inspect_evidence, check_invariants, trace_provenance and assess_vault_readiness. GitHub Copilot displays the server name as a prefix, for example walletwall-resolve_asset.
2

Eleven resources

The server lists eleven walletwall:// resources. A server that lists six is an older build.
3

Read the conformance resource

Read walletwall://conformance/version. It reports the WWEP, registry, policy and rules versions and the content digests of the bundled registry, policies and specification.

Run the Quickstart

Exercise the real server with synthetic evidence and no WalletWall-hosted runtime.

Understand WWEP

Learn what the states mean before using them in an application.

Optional: loopback HTTP

stdio is the default and the only transport inside the published packages. If a client can connect only over HTTP, the source repository also contains an optional Streamable HTTP adapter bound to 127.0.0.1 by default. You run it yourself; WalletWall does not host it.

Claude / local HTTP adapter

When to use the adapter, how to run it, and the security boundary around its unauthenticated port.

Package, registry and version details

WalletWall is listed as io.github.Wallet-Wall/walletwall in the official MCP Registry. The registry hosts metadata only; the MCPB package is a GitHub Release asset.Query the listing yourself:
The listing’s repository and package URLs still use the former repository name, walletwallrus-copilot; GitHub redirects them. The older 0.2.0 package serves six resources and no shape diagnostics, so prefer 0.2.1.
The MCPB contains manifest.json, server/walletwall-mcp.mjs, LICENSE and THIRD_PARTY_NOTICES.md. Before using a downloaded package, compare its digest with the Registry listing:
A digest match identifies the bytes named by the listing; it is not a signature or certification. In the source repository, npm run verify:bundle rebuilds the server and npm run verify:mcpb repacks the MCPB and compares the deterministic digests.
Versions at the time of writing (November 2026):Version strings do not pin the MCP surface: older builds have reported the same engine or plugin version while serving six resources instead of eleven. When exact behavior matters, inspect the server you are actually running: count its resources and read walletwall://conformance/version.

Uninstall

The WalletWall stdio server writes no cache or query history of its own. Your client’s plugin directories and logs are managed by your client.

Where to go next

GitHub Copilot

The plugin’s four skills, the WalletWall canvas and its trust boundary.

Claude / local HTTP adapter

The Claude Code plugin and the optional loopback adapter.

Privacy & Security

What runs where, and what your AI client and model provider can see.

Troubleshooting

Discovery and configuration problems, by symptom.