OpenChainGraph Suite · Digital-Asset Rails

Stablecoin Reserve Scorecard

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

Merkle-sum Proof-of-Reserves verification feeding a MiCA reserve disclosure check, presented as one dated scorecard over an issuer's published attestation. Both checks are backward-looking and deterministic; each keeps its own not_proven scope and neither is merged into a single verdict.

OpenChainGraph · 2 Steps compliance mandate Hash-Anchored chain_depth:2 Client-Side · Zero PII
Chain Topology: Stablecoin Reserve Scorecard
Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT node
Reserve Proof Verifier art-280-reserve-proof-verifier
reserve_proof_determination and not_proven feed the disclosure-level coverage, composition, segregation and cadence check as corroborating cryptographic evidence of the same reserve; each check keeps its own not_proven scope, never merged into a single verdict
MCP Call · verify_reserve_proof
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "verify_reserve_proof",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 TERMINAL node
Check MiCA Reserve Disclosure art-512-check-mica-reserve-disclosure
coverage, composition, segregation and cadence findings, plus the caller-declared rule set they were checked against, feed the scorecard's export; terminal stage
MCP Call · check_mica_reserve_disclosure
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_mica_reserve_disclosure",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
Export Artifacts
Download the chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition; no new hash is minted. Available after hash computation.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: The issuer June reserve disclosure is in. Does the declared reserve mix still cover tokens in circulation under MiCA?
Run the AINumbers MCP tool `run_chain` with {"chain":"stablecoin-reserve-scorecard"} and read `art-512-check-mica-reserve-disclosure.segregation.meets_declared_minimum`.
Re-run with `inputs` for `art-512-check-mica-reserve-disclosure`, reusing the values that result echoed, with `token_type` set to "ART". Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/stablecoin-reserve-scorecard.html