WalletWall
io.github.Wallet-WallPublished by GitHub account Wallet-Wallv0.2.1Updated Nov 2, 2026
Stablecoin intelligence and vault readiness through WalletWall MCP.
The publisher's own server: Wall Marketing
Overview
Local, offline, read-only MCP server that lets an assistant inspect stablecoin identity, evidence lineage, conflicts and vault readiness.
- What you can do
- Resolve stablecoin assets by chain ID and address, or by symbol candidates
- Normalize observations into canonical form with digests and exact decimal rendering
- Inspect evidence support, freshness, finality, authority, limitations and conflicts per assertion
- Check the WWEP invariants and declared-versus-computed values
- Trace source provenance for a single assertion
- Assess vault technical readiness against a draft ruleset
- When to use it
- Useful when you want an assistant to reason about stablecoin identity and the evidence behind claims, or to check vault-readiness signals, without live chain access. It suits review and due-diligence style questions where the assistant should state what sources support and where limitations lie.
- Requirements
- Runs as a local stdio process and requires node on PATH. Distributed as a Copilot plugin from the project's GitHub repository or a local checkout; the bundled registry is a fixed snapshot, and nothing is fetched at runtime. An optional loopback HTTP adapter for a user-owned Claude Managed Agent is available from a source checkout.
Installation
In SourceWeft
- Open WalletWall in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
WalletWall
Stablecoin intelligence and vault readiness for GitHub Copilot.
WalletWall is a local, read-only Copilot plugin and MCP server for inspecting stablecoin identity, source lineage, conflicts and vault-readiness signals.
Status: Pre-release
WWEP: 0.1
Registry: point-in-time verified
WalletWall does not sign, custody, trade, broadcast transactions, provide investment advice or certify regulatory compliance. Nothing here has been published to npm or a Copilot marketplace. Source and release artifacts are on GitHub Releases (v0.2.0), and the local MCP server's metadata is listed in the official MCP Registry as io.github.Wallet-Wall/walletwall.
Inspect stablecoin identity, wallet state, source lineage, conflicts, and vault readiness through WalletWall MCP.
What you get
[WalletWall canvas showing a conflict]
What it will not say
A support state such as ESTABLISHED means the presented evidence satisfies a published policy. It does not mean the evidence is true.
WalletWall reports what identified sources and authority policies support. A supported result does not guarantee that upstream information is correct.
The bundled registry (five stablecoin deployments on Ethereum, Base and Arbitrum) is a point-in-time snapshot verified on 2026-10-24. It is not live or current-chain data. WalletWall fetches nothing at runtime. See docs/REGISTRY_SOURCES.md.
Privacy
WalletWall-controlled code does not retain MCP query history or transmit query data to WalletWall infrastructure. GitHub Copilot and the selected model provider may independently process prompts and tool data under their own policies.
Wallet addresses you put in a prompt are processed by Copilot and the model provider, not by WalletWall. Details and the limits of what is tested: PRIVACY.md, docs/PLUGIN_PATH_PRIVACY.md.
Install
From this repository on GitHub (verified with GitHub Copilot CLI 1.0.103 against the public repository, with no credentials):
Or from a local checkout:
The marketplace and the plugin are both named walletwall. Verified with GitHub Copilot CLI 1.0.103: copilot plugin list --json reports walletwall from marketplace walletwall, version 0.2.0. This repository is the plugin source only; the plugin is not an accepted listing in any GitHub or Copilot marketplace or catalog. The official MCP Registry listing covers the MCP server's metadata only and is discovery, not endorsement or certification.
In the GitHub Copilot app: Customize → Plugins → marketplace settings → add this repository → Install. A new session then has the six WalletWall MCP tools, the skill and the WalletWall canvas. What was verified on Windows and what was not: docs/DESKTOP_INSTALL_PROOF.md. Requires node on PATH.
Claude Managed Agent (optional)
The shipped Copilot MCP remains stdio-only. For a user-owned Claude Managed Agent, a separate opt-in loopback Streamable HTTP adapter is available from a source checkout:
It exposes http://127.0.0.1:8787/mcp for connection through the user's own Anthropic MCP tunnel. The adapter lives outside the packages/mcp publish surface, is not part of the bundled Copilot runtime, does not create a WalletWall-hosted endpoint, and does not change the six-tool WalletWall MCP contract. See docs/CLAUDE_MANAGED_AGENT.md.
Develop
Requires Node.js 22.18 or newer (tested on 24).
Generated files are committed and verified in CI on Linux and Windows. See CONTRIBUTING.md for which command regenerates what.
Documents
CONTRIBUTING.md · SECURITY.md · PRIVACY.md · BOUNDARIES.md · THREAT_MODEL.md · DATA_SOURCES.md · docs/REGISTRY_SOURCES.md · docs/DEPENDENCY_POLICY.md · docs/PUBLIC_RELEASE_AUDIT.md · docs/PUBLIC_DISCOVERY_READINESS.md · docs/CLAUDE_MANAGED_AGENT.md · TRADEMARKS.md · LICENSE
Layout: plugin/ (the plugin), packages/mcp/ (engine, registry, authority policies, tests), spec/ (WWEP 0.1 draft), conformance/ (conformance and adversarial corpus), security/ (manifests and hashes), evals/ (Copilot agent evals, separate from conformance), docs/.
License
Apache License 2.0 (LICENSE), copyright 2026 WalletWall. The license covers the software and documentation in this repository. It does not grant rights to the WalletWall name, logos or marks: see TRADEMARKS.md. Third-party components keep their own licenses (plugin/THIRD_PARTY_NOTICES.md).
Source: README.md at commit 770ed9d
Tools
0Version history
2- v0.2.1LatestOct 26, 2026
- v0.2.0Oct 25, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Wall integrations
Wall Marketing
marketing.wallOfficial publisher
Wall Marketing's remote MCP server lets an AI assistant book adverts on e-paper screens in venues, host a screen, or earn commission signing venues up.
SonicWall MCP
Published by GitHub account Servosity
Local MCP server and CLI that lets an assistant audit SonicWall firewall fleets in NSM for firmware, advisories, MFA and SSL-VPN exposure.
The Button Wall
Published by GitHub account leovenom
Local MCP server for The Button Wall that lets an assistant check wall availability, quote a button, find free spots and create a Stripe checkout link.