Single-node D0 diagnostic scoping a CASP's MiCA Title-V lifecycle readiness and routing to the right Wave-20 mica-* chain; ART/EMT-issuer cases route to the existing stablecoin chains.
run_mica_casp_fit{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "run_mica_casp_fit",
"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: We plan to passport custody services into the EU. What readiness grade would our current MiCA posture earn?
Run the AINumbers MCP tool `run_chain` with {"chain":"mica-fit"} and read `art-98-mica-casp-fit-diagnostic.readiness_grade`.
Re-run with `inputs` for `art-98-mica-casp-fit-diagnostic`, reusing the values that result echoed, with `inputs` changed so the posture is authorisation-stage with own funds and MAR arrangements in place. 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/mica-fit.html