Map parent and child licenses into canonical rights vectors, compare them across frameworks, and produce a compatibility verdict with reason codes and the required child license. Use as a standalone entry point when you only need to know whether a derivative work can legally adopt a given license, or embed it as steps 2 and 3 of the full IP License Election and Attestation workflow.
compare_rights_matrix{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "compare_rights_matrix",
"arguments": {}
},
"id": 1
}
check_license_compatibility{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "check_license_compatibility",
"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 library ships under a share-alike license. May a proprietary module build on it?
Run the AINumbers MCP tool `run_chain` with {"chain":"license-compatibility-check"} and read `art-204-license-compatibility-checker.compatible`.
Re-run with `inputs` for `art-204-license-compatibility-checker`, reusing the values that result echoed, with `child_license` changed so the child is CC-BY-NC-4.0 while parent_license is CC-BY-SA-4.0. 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/license-compatibility-check.html