ots_calendar_health

Active

declared in 0.8.0

Live health of the public OpenTimestamps (OTS) timestamp-anchoring calendar servers — the aggregation-and-anchoring infrastructure behind tamper-evident, independently verifiable, Bitcoin-anchored timestamps. Answers "are the public timestamp calendars up and still anchoring right now?" before an agent trusts a fresh proof. `calendar` = "all" (default — probe every public calendar and return an overall verdict) | "alice" | "bob" | "finney" (Eternity Wall) | "catallaxy". Per calendar: live reachability + latency (our own probe), server version, pending commitments, anchor transactions waiting for confirmation, the calendar's best-block height (its Bitcoin chain view), average time between anchor transactions over the last week (anchoring cadence), and the operational wallet balance funding anchor transactions; the overall verdict flags any calendar whose height lags the consensus (a stalled chain view / paused anchoring). Source: Dynamic Feed's own availability probes + each calendar's public status page (measured facts, like cert_check / service_status). Keyless, 120 s cache. Operational balances are anchoring-funding health signals, NOT market prices. Every value is returned in an Ed25519-signed, provenance-stamped envelope (source and observation time) you can verify offline against /.well-known/keys, no account required.

Parameters schema

{
  "type": "object",
  "title": "ots_calendar_healthArguments",
  "properties": {
    "calendar": {
      "type": "string",
      "title": "Calendar",
      "default": "all"
    }
  }
}

What this tool wraps· 0 endpoints

min confidence0.70 0.50

No endpoints wrapped at confidence ≥ 0.50.

Parent server

ai.dynamicfeed/dynamic-feed

1/7 registries

View full server →