W-G chain. Validate CCTP v2 cross-chain USDC transfer — fires when ≥2 Arc fit dimensions score >0.
run_arc_fit_diagnostic{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "run_arc_fit_diagnostic",
"arguments": {}
},
"id": 1
}
validate_cctp_v2_transfer{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "validate_cctp_v2_transfer",
"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: Treasury queued a burn-and-mint to a chain missing from the operations runbook. What does the transfer check say about that destination?
Run the AINumbers MCP tool `run_chain` with {"chain":"arc-cctp-transfer"} and read `art-47-arc-cctp-transfer.verdict`.
Re-run with `inputs` for `art-47-arc-cctp-transfer`, reusing the values that result echoed, with `dest_domain` set to "moonbeam". 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/arc-cctp-transfer.html