ART-733 · OpenChainGraph · Servicing Compliance Clock
v1.0.0

Servicing Compliance Clock

Computes servicer-compliance due dates and clock states from the event dates and loan values you type in: error-resolution and information-request clocks, loss-mitigation acknowledgment and evaluation, the 37-day pre-sale boundary, the 120-day pre-foreclosure bar, no-duplicate processing, force-placed-insurance notice, reminder, cancel and refund clocks, payment-crediting and payoff-statement deadlines, and ARM notice windows with their exception branches. Every obligation carries its paragraph citation and a named business-day calendar assumption. Dates that are invalid or ambiguous, rescinded rule branches, and over-bound event sets are refused and never computed.

Policy Mandate Export Consumer Finance consumer_finance Proof verified
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data: use synthetic or anonymised values only; this tool accepts event dates and numeric values only and refuses any text field or impossible date.
Result

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.

Run the AINumbers MCP tool `servicing_compliance_clock`. Task: Compute servicer-compliance due dates and clock states from event dates and loan values across the Regulation X/Z servicing rules: error-resolution, information-request, loss-mitigation, foreclosure-timeline, force-placed-insurance, reminder, cancel, refund, payment-crediting, payoff-statement and ARM notice clocks.
Call it with arguments: {"policy_parameters":{"events":[{"rule":"error_acknowledgment","trigger_date":"2026-11-25"}]}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string, or re-run the in-page WebMCP tool `servicing_compliance_clock`.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Over MCP, the run happens on the AINumbers worker. No AINumbers server stores your inputs.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/733-servicing-compliance-clock.html#p=v1.H4sIAAAAAAAA_wFIALf_eyJldmVudHMiOlt7InJ1bGUiOiJlcnJvcl9hY2tub3dsZWRnbWVudCIsInRyaWdnZXJfZGF0ZSI6IjIwMjYtMTEtMjUifV19cerJJUgAAAA