Single-node D0 diagnostic scoring a firm's readiness for the EU/UK/CH T+1 move (11 Oct 2027) and the Dec-2026 allocation/confirmation timing mandate, routing to the right Wave-17 sd-* chain.
run_t1_readiness_diagnostic{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "run_t1_readiness_diagnostic",
"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: Budget covers automating one T+1 workstream this quarter. Which readiness dimension does automating matching alone lift?
Run the AINumbers MCP tool `run_chain` with {"chain":"settlement-discipline-fit"} and read `art-77-t1-settlement-readiness-diagnostic.dim_scores.matching.score`.
Re-run with `inputs` for `art-77-t1-settlement-readiness-diagnostic`, reusing the values that result echoed, with `matching_method` set to "auto". 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/settlement-discipline-fit.html