Single-node diagnostic linting an extracted monthly reserve disclosure against GENIUS Act S.394 §4: composition, tenor, custody, certification, examiner, month-over-month diff, on-chain supply cross-check.
check_genius_reserve_disclosure{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "check_genius_reserve_disclosure",
"arguments": {}
},
"id": 1
}
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 monthly reserve disclosure is drafted. Will it pass the GENIUS monthly check as written, or does something in the pack still fail?
Run the AINumbers MCP tool `run_chain` with {"chain":"genius-reserve-disclosure"} and read `art-275-genius-reserve-disclosure-checker.monthly_disclosure_determination`.
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/genius-reserve-disclosure.html