Connect WalletWall
Install the local server in GitHub Copilot, Claude Code or another MCP client.
Get a result
Run synthetic evidence end to end and see WalletWall refuse to guess when evidence is missing.
What problem it solves
Answers about stablecoins often blur what was observed with what was assumed: a ticker symbol treated as identity, a provider’s number treated as canonical chain state, a failed lookup turned into zero, or two disagreeing readings quietly collapsed into one. WalletWall keeps those distinctions explicit. It reports which evidence was presented, where it came from, which policy applied, whether it was fresh and final, and whether other evidence conflicts with it. When required evidence is missing, the result stays weak instead of being filled in.The mental model
ESTABLISHED means the presented evidence satisfies the published policy for this claim type. It
does not mean WalletWall proved the underlying fact true.How it fits together
The server is a pure function of the bundle you send, the evaluation time you send, and the registry, policies and rules bundled into it. It opens no network connection, writes no files, reads no environment variables and keeps no query history. Your MCP client and model provider do see every tool input and output: see Privacy & Security.What ships
- Six tools for registry lookup, normalization, evidence evaluation, invariant checks, provenance and vault technical-readiness assessment. See Tools.
- Eleven resources containing the evidence contract, policies, registry, versions and synthetic examples. See Resources.
- WWEP 0.1 (draft), the WalletWall Evidence Profile behind every result. See Evidence Model (WWEP).
- GitHub Copilot and Claude Code integrations, both running the engine locally.
- WallPrint 0.1, a separate disclosure contract and public resolver for records WalletWall deliberately publishes. Calling MCP never publishes a WallPrint.
Installable today — pre-release
Not part of the product
These capabilities are deliberately absent from WalletWall MCP, and no page in this section describes them as available.- No WalletWall-hosted MCP endpoint, remote transport, managed agent or hosted inference.
- No live data retrieval inside the engine. You supply the evidence; WalletWall evaluates it.
- No transaction capability of any kind: no keys, signing, custody, trading, transaction construction, broadcasting or vault execution.
- No signatures or attestations on WallPrint records. A digest proves bytes, not authorship or factual truth.
- No certification. Results do not certify regulatory compliance, solvency, safety or audit status.
Status
WalletWall MCP is pre-release. WWEP 0.1 and WallPrint 0.1 are WalletWall-defined drafts, not industry standards, and neither the specification nor the code has had an independent security review or audit. Version domains move independently; Install & Connect shows how to inspect the server you are actually running.How this relates to the WalletWall application
The hosted application at walletwall.org and the MCP server share a discipline, not a runtime. The application fetches data from providers and scheduled snapshots and labels every response with its source; the MCP server fetches nothing and evaluates the evidence you present. The application’s Wallet Evidence Model and the server’s Evidence Profile are different schemas built on the same rule — unknown is never zero, and a source’s authority is never inferred from how its bytes arrived. The same rule governs how WalletWall reasons about independent authority in its own assurance work.Data Serving Architecture
How the hosted application sources and labels its own data, for contrast with the bring-your-own-evidence model here.
What you can use today
Where the MCP server, the plugins and WallPrint sit among WalletWall’s surfaces by maturity.
Where to go next
Install & Connect
Connect the local server to your MCP client.
Quickstart
Run a synthetic example and see the fail-closed behavior first.
Evidence Model (WWEP)
Understand sources, observations, assertions and evidence states before diving into the reference.
WallPrint
Learn where local evaluation ends and deliberate publication begins.
Tools
Reference for the six read-only tools.
Resources
Reference for the eleven static resources.
GitHub Copilot
Install the plugin, use its four skills and open the WalletWall canvas.
Claude / local HTTP adapter
Use the Claude Code plugin or the optional user-run loopback adapter.
Privacy & Security
Understand exactly what runs where and what your model provider can see.
Troubleshooting
Diagnose setup, evidence and resolver problems by symptom.

