Eclipse Sandclock runs on your own machine — the client starts it, so there is no endpoint to ping.
Eval-expiry clock over fixture Benchkit scorecards + fixture drift evidence; local stdio MCP only.
The linked repository no longer exists on GitHub — it was deleted or made private.
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Alternatives to Eclipse Sandclock
same job, measured the same wayDecision-evidence sealing + audit recompute over fixture decisions; local only.
Per-action-class sponsor acceptance receipts over fixture sponsors/parties, local stdio only.
Fixture cyber-insurance evidence assembly with change receipts; local only, not underwriting.
Band-only age proofs over fixture attestations, sealed to one mandate; local only.
Signed death record triggers atomic cascade expiry of fixture instruments; local only.
Guardian veto verdicts + receipts over fixture actions; local/simulator only.
Failure-attribution recompute over hash-chained fixture records (local only): verdict + proof path.
Fixture payee drift evidence; pinned fixture keys, not public keys; export packs not value-free.
Eclipse Sandclock — questions
Answers built from our own checks of this server.