EuGB factsheet (Annex I) + allocation report (Annex II) completeness + proceeds-alignment validation (ART-75) -> use-of-proceeds Taxonomy alignment cross-check (ART-73) -> Merkle integrity over the bond evidence set (cry-04). The issuer-to-external-reviewer green-bond conformance pack. Decision-support draft, not a reviewer attestation.
validate_eugb_factsheet{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "validate_eugb_factsheet",
"arguments": {}
},
"id": 1
}
score_taxonomy_alignment{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "score_taxonomy_alignment",
"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: The allocation report landed this morning. With it on file, does the Annex II leg of our European green bond pack finally read complete?
Run the AINumbers MCP tool `run_chain` with {"chain":"eugb-conformance"} and read `art-75-eugb-factsheet-validator.annex_ii_status`.
Re-run with `inputs` for `art-75-eugb-factsheet-validator`, reusing the values that result echoed, with `allocation_report` set to "complete". 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/eugb-conformance.html