Validate a tokenized money-market fund as eligible collateral for Canton settlement. Fund-level NAV and eligibility check → HQLA tier and haircut verdict.
This page is the chain definition (plan). To run the chain step by step in your browser, with each step's kernel executing in-page and a composite hash over the outputs, open the live runner:
▶ Run this chain in your browservalidate_fund_collateral{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "validate_fund_collateral",
"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: Can this tokenized money market fund be pledged as collateral, or do its liquidity and NAV terms make it ineligible?
Run the AINumbers MCP tool `run_chain` with {"chain":"canton-mmf-collateral"} and read `514-tokenized-fund-collateral-validator.eligibility`.
Re-run with `inputs` for `514-tokenized-fund-collateral-validator`, reusing the values that result echoed, with `fund_type` changed so fund_type is sec_inst_prime_mmf with nav still 1. 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-mmf-collateral.html