Verifies the two most-cited emerging agent-identity primitives in sequence: a did:webvh DID log's hash-chain and update-key authorization, then an ACDC credential chain's SAID integrity and issuer-to-issuee edge linkage back to a stated root AID. Verify-only across both steps; neither tool operates witness/registry infrastructure.
verify_did_webvh_log{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "verify_did_webvh_log",
"arguments": {}
},
"id": 1
}
verify_acdc_delegation_chain{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "verify_acdc_delegation_chain",
"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: An agent presents a chained delegation for a payment scope. Does every hop verify, and does the chain root at the controller we issued?
Run the AINumbers MCP tool `run_chain` with {"chain":"verify-agent-delegation"} and read `art-285-acdc-delegation-chain-verifier.valid`.
Re-run with `inputs` for `art-285-acdc-delegation-chain-verifier`, reusing the values that result echoed, with `expected_root_aid` set to "EAlt-controller-AID-0000000000000000000000000". 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/verify-agent-delegation.html