Art 6/8 whitepaper Annex I completeness + iXBRL / ESMA MiCA taxonomy conformance (ART-102) -> Merkle integrity (cry-04). A hash-anchored conformance target distinct from any shipped tool.
lint_crypto_asset_whitepaper{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "lint_crypto_asset_whitepaper",
"arguments": {}
},
"id": 1
}
verify_merkle_batch{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "verify_merkle_batch",
"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: Our whitepaper draft is due at the regulator. What conformance grade does the linter give once every required section is complete?
Run the AINumbers MCP tool `run_chain` with {"chain":"mica-whitepaper"} and read `art-102-crypto-asset-whitepaper-linter.conformance_grade`.
Re-run with `inputs` for `art-102-crypto-asset-whitepaper-linter`, reusing the values that result echoed, with `inputs` changed so all ten sections are complete and iXBRL validates. 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-whitepaper.html