Validate a DTCC/ComposerX tokenized U.S. Treasury for issuance and atomic settlement. Treasury/DTC-custody-specific; not generic securities lifecycle, not FICC clearing economics.
classify_digital_asset_regulatory{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "classify_digital_asset_regulatory",
"arguments": {}
},
"id": 1
}
validate_dtc_tokenized_treasury{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "validate_dtc_tokenized_treasury",
"arguments": {}
},
"id": 1
}
validate_canton_dvp_atomicity{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "validate_canton_dvp_atomicity",
"arguments": {}
},
"id": 1
}
check_tokenized_collateral_eligibility{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "check_tokenized_collateral_eligibility",
"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: Before we tokenize this Treasury CUSIP class, is the DTC custody and Fed eligibility pack ready for issuance, or are there gaps?
Run the AINumbers MCP tool `run_chain` with {"chain":"canton-dtc-treasury"} and read `art-109-dtc-tokenized-treasury.verdict`.
Re-run with `inputs` for `art-109-dtc-tokenized-treasury`, reusing the values that result echoed, with `tokenized_ust_config` changed so fed_eligible is false. 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/canton-dtc-treasury.html