- An error (
isError: true, or a JSON-RPC error) means the server could not accept your request: a tool name, a resource URI or an input it does not recognise. - A weak result (
NOT_ESTABLISHED,UNKNOWN,PARTIAL,STALE,CONFLICTING) is a successful answer about your evidence. It is not a bug, and it should not be retried away.
Discovery and setup
The tools do not appear in GitHub Copilot
The tools do not appear in GitHub Copilot
- Start a new session. A session that was open during the install does not gain the plugin.
- Run
copilot plugin list --jsonand check thatwalletwallfrom marketplacewalletwallis listed and enabled. - Run
copilot mcp listand check thatwalletwallappears among the plugin servers as a local server. - Check that
node --versionworks in the environment Copilot runs in, and reports 22.18 or newer. - Install with the current names: the marketplace and the plugin are both
walletwall, so the command iscopilot plugin install walletwall@walletwall. Historical install records in the repository mention an earlier marketplace name; do not copy it.
Claude Code does not load the plugin
Claude Code does not load the plugin
claude --plugin-dir . from inside the walletwall-claude clone, or pass the clone’s path
explicitly. The directory must contain .claude-plugin/plugin.json, .mcp.json,
server/walletwall-mcp.mjs and node_modules/ (the server loads the SDK and zod from it). Check
that node on your PATH is 22.18 or newer.My MCP client starts the server, but it fails or exits
My MCP client starts the server, but it fails or exits
- The command must be
node, and its single argument the absolute path towalletwall-mcp.mjs. Relative paths resolve against whatever directory your client starts in. - In JSON on Windows, escape backslashes (
C:\\Users\\...) or use forward slashes. - Add no arguments and no environment variables: the server ignores both, and a wrapper script that prints anything to standard output corrupts the stdio protocol.
- If the process dies, its only message on standard error is the fixed line
walletwall-mcp: fatal error. Run the same command by hand to see whethernodeitself reports a problem.
Running the server by hand prints nothing and does not exit
Running the server by hand prints nothing and does not exit
Which Node.js version do I need?
Which Node.js version do I need?
walletwall-mcp.mjs) needs no npm install. The
loopback HTTP adapter runs the repository’s TypeScript source directly, so it additionally needs
npm ci in the walletwall-copilot checkout, and Node.js 22.18 or newer to run .ts files.Names and URIs
UNKNOWN_TOOL
UNKNOWN_TOOL
resolve_asset, normalize_observation,
inspect_evidence, check_invariants, trace_provenance, assess_vault_readiness. GitHub
Copilot displays them with a walletwall- prefix, but the protocol name has none. There is no tool
for signing, sending, approving, swapping or fetching data, and asking for one returns
UNKNOWN_TOOL.Unknown resource.
Unknown resource.
walletwall://schemas/claims, not walletwall://schema/claims.
The eleven URIs are listed on Resources. Asking for resource templates or for
prompts returns Method not found, because the server offers neither; that is expected.Rejected input
INVALID_INPUT: Input failed schema validation.
INVALID_INPUT: Input failed schema validation.
issues list gives the path and the issue code of each problem, never the value you sent:*, and array positions as #. Compare
your input with walletwall://schemas/evidence and walletwall://schemas/claims. A second message,
Input structure is not permitted. with no issues, means the input is nested more than 12 levels
deep, holds more than 20,000 values, or has a constructor or prototype key.INVALID_QUANTITY
INVALID_QUANTITY
normalize_observation refuses a balanceAtomic larger than 2²⁵⁶ − 1, a decimals greater than
36, and a VALUE observation without both balanceAtomic and decimals. A spelling that is not a
canonical atomic-unit decimal string at all (a sign, a decimal point, a leading zero) is rejected
earlier, as INVALID_INPUT.Timestamps are rejected
Timestamps are rejected
Z suffix, for example 2026-10-23T12:00:30Z, optionally with milliseconds. Offsets
such as +02:00 and impossible dates are rejected.Weak or unexpected results
An assertion is NOT_ESTABLISHED with INVALID_SUBJECT, SUBJECT_MISMATCH, INVALID_VALUE or VALUE_MISMATCH
An assertion is NOT_ESTABLISHED with INVALID_SUBJECT, SUBJECT_MISMATCH, INVALID_VALUE or VALUE_MISMATCH
diagnostics: they name the record checked and
its required, missing, invalid, unexpected (*) and mismatched keys. Rebuild the bundle from
walletwall://schemas/claims, and treat the rebuilt bundle as new input, not as the original.NOT_ESTABLISHED with NO_SOURCE
NOT_ESTABLISHED with NO_SOURCE
observationIds. If the assertion also carries a value, check_invariants reports
INV-01 (NO_SOURCE_PRESENTED_AS_FACT): with no source, the value must be null.UNKNOWN with NO_RESULT
UNKNOWN with NO_RESULT
NO_RESULT or ERROR. That is the correct way to
record a failed or empty lookup from your own provider: it is unknown, not zero. Keep the
assertion’s value null; keeping a value reports INV-01 (NO_RESULT_AS_VALUE), or INV-04 /
INV-05 for a zero or false value.PARTIAL when I expected ESTABLISHED
PARTIAL when I expected ESTABLISHED
NO_AUTHORITATIVE_OBSERVATION means no observation came from an origin that
may establish the claim: an asset’s identity, for example, needs an AUTHORITY_ATTESTED observation
from an ISSUER_PUBLICATION source whose authorityId matches the registry. A registry match from
resolve_asset is PARTIAL at best. INSUFFICIENT_INDEPENDENT_CORROBORATION means fewer
independence groups support the claim than its policy requires: a single source, or several sources
in one group.SUPPORTED with NOT_FINALIZED or FINALITY_UNKNOWN
SUPPORTED with NOT_FINALIZED or FINALITY_UNKNOWN
NOT_FINALIZED), or with unknown finality
(FINALITY_UNKNOWN), cannot be ESTABLISHED. Use a reading taken at a finalized block.STALE, or UNKNOWN_FRESHNESS
STALE, or UNKNOWN_FRESHNESS
evaluatedAt you send. A CURRENT claim older than its policy’s
maximum age (30 days for asset identity, 120 seconds for a current balance, 300 seconds for a price)
is STALE. An observation timestamped after evaluatedAt gives UNKNOWN_FRESHNESS with
OBSERVATION_FROM_FUTURE: check the clock and the time zone of the tooling that produced the
reading.CONFLICTING
CONFLICTING
Readiness is NOT_ESTABLISHED or CRITERIA_NOT_MET
Readiness is NOT_ESTABLISHED or CRITERIA_NOT_MET
criteria. INDETERMINATE criteria give NOT_ESTABLISHED; any NOT_MET gives
CRITERIA_NOT_MET. If every criterion says REQUIRED_INPUT_ASSERTION_MISSING_OR_WRONG_CLAIM_TYPE,
identityAssertionId and balanceAssertionId are missing or swapped: the first must name an
ASSET_IDENTITY assertion and the second a TOKEN_BALANCE_AT_BLOCK assertion.The same address is treated as two subjects
The same address is treated as two subjects
0xA0b8… and 0xa0b8… are two
subjects. Use lowercase addresses throughout; normalize_observation lowercases them for you.My data provider failed or returned something odd
My data provider failed or returned something odd
NO_RESULT or ERROR rather than leaving it out or writing zero, and record how each reading
arrived in transport.retrievedVia.Loopback HTTP adapter
Nothing answers on the port
Nothing answers on the port
{"status":"ok"} means the adapter is up. If the adapter exited immediately with
walletwall-mcp-http: fatal error, the port may be in use, the port value may be invalid, or
--host was given something other than 127.0.0.1 or 0.0.0.0.400, 403, 405, 413, 414 or 415
400, 403, 405, 413, 414 or 415
/health works, but /mcp responses are malformed
/health works, but /mcp responses are malformed
/health answers correctly but MCP calls fail with errors about an invalid chunked response,
something between the client and the adapter is rewriting local HTTP traffic. Security software
that inspects HTTP connections can do this even on 127.0.0.1. Try from a different environment
(for example WSL on Windows), or exclude the loopback adapter from that inspection.WallPrint resolution
DIGEST_MISMATCH, MALFORMED_REFERENCE or UNSUPPORTED_VERSION
DIGEST_MISMATCH, MALFORMED_REFERENCE or UNSUPPORTED_VERSION
DIGEST_MISMATCH: the record is published under other bytes than the digest in your reference. Every digest is printed, and the published version is offered as a link. It is an integrity finding, not an accusation of forgery.MALFORMED_REFERENCE: the reference text was altered or truncated. References have exactly one valid spelling; copy them exactly.UNSUPPORTED_VERSION: only reference and WallPrint version0.1resolve today.
UNREACHABLE
UNREACHABLE
walletwall.org.Still stuck?
Open an issue onWallet-Wall/walletwall-copilot
with the tool or resource involved, the error code and issues, and the output of
walletwall://conformance/version. Use synthetic values only, and never include a real wallet address,
key or credential. For security problems, follow Privacy & Security instead.
