Horizon Fidelity Monitor

Install

Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install connector/leocelis-horizon-fidelity-monitor

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

1 read · 5 write · 0 delete · 4 not yet classified

Secrets

1 (API keys, tokens or passwords)

Install scripts

Nothing to install (hosted)

Runs as

Hosted (remote endpoint)

Tools (10)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• associate_missionBind this session to a mission

  Bind `session_id` to `mission_id` so that mission's due signals (post-cap, at most one new per turn) start arriving in process_turn's active_events, tagged plane="mission". Without this call, a configured mission store still emits ZERO events into this session. Call at the start of any conversation that concerns a known mission, before the first clock_status. This is the Memento Mori MISSION plane, not the conversation monitor: surface this to the operator with its numbers; never absorb it silently. See docs/integrations/MEMENTO_MORI_AGENTS.md §1-2.

• clock_ackAcknowledge a fired mission signal

  Move the (item_id, signal_type) alarm state machine to ACKED, recording `actor`. Call this ONLY on the operator's explicit acknowledgement of that exact signal — never self-ack to quiet a signal you find repetitive; the engine already caps and edge-triggers, and silence belongs to the operator, not the agent. Authorization is enforced by host rules, not by this tool. This is the Memento Mori MISSION plane, not the conversation monitor: surface this to the operator with its numbers; never absorb it silently. See docs/integrations/MEMENTO_MORI_AGENTS.md §1-2.

• clock_closeRetire a mission item (closed or superseded)

  Mark an item `closed` (done or abandoned) or `superseded` (replaced by another item — pass `superseded_by`). By default the whole subtree under it is retired too (`cascade=true`), so a mission's deadlines, gates and tasks stop firing with it. Nothing is deleted: the rows stay on clock_status with their status, for history. The horizon root cannot be closed. Call this ONLY on the operator's explicit instruction to retire that item — a signal you find noisy is acked, never closed. This is the Memento Mori MISSION plane, not the conversation monitor: surface this to the operator with its numbers;…

• clock_progressRecord a mission progress/stage/artifact event

  Append one event (kind: progress | stage_enter | stage_exit | artifact | ratify | ack) to an item's bitemporal log. `event` carries kind, valid_time (ISO 8601, when the fact happened), and optionally stage, wait_or_touch, payload, correction_of, and provenance (required for kind=artifact: source_system, native_id, raw_timestamp). Record this as a side effect of real work in the SAME turn — never a separate logging session, never a fabricated or assumed event. This is the Memento Mori MISSION plane, not the conversation monitor: surface this to the operator with its numbers; never absorb it sil…

• clock_proposeInert TTL or break-even proposal from recorded history

  kind='ttl': nearest-rank `percentile` (default P80) over the caller-supplied `completed_durations_days` — an empty list returns proposal=null, never an invented default. kind='breakeven': cost_setup, rate, setup_hours, delta_t_hours, lam_per_day (all caller-measured) at `timestamp`. Either way the return is {item_id, kind, value, sample_size, derivation} and is INERT: nothing is applied until an explicit clock_progress(kind=ratify) write. Present the derivation and sample size; the operator ratifies. This is the Memento Mori MISSION plane, not the conversation monitor: surface this to the oper…

• clock_registerRegister or update a clocked mission item

  Create a rooted-tree item (kind: horizon | mission | task | deadline | gate | entity | deferral | probe) in the mission store. `item` carries kind, title, created_valid (ISO 8601), and kind-specific fields (end_date, revisit_date, ttl_start/ttl_end, deadline_date, deadline_kind, gates_item_id, age_budget_days, stall_days, namespace, amount, parent_id). Schema violations (undated deferral, root-less item, unflagged person namespace, duplicate/non-finite root, ...) return a typed {error_type, rule, fix} — relay it to the operator verbatim, never route around it; e.g. an undated deferral means as…

• clock_statusFull mission clock surface

  Return the ClockReport for `timestamp` (the host-injected evaluation instant; ISO 8601 — omit only when you genuinely have no clock): ages, TTL states, latencies, horizon shares, path comparisons, and money (only when a rate is declared). Optional `scope` (a mission_id) filters the report to that mission's subtree. Open your first substantive reply for an associated mission with any red state here, numbers included. This is the Memento Mori MISSION plane, not the conversation monitor: surface this to the operator with its numbers; never absorb it silently. See docs/integrations/MEMENTO_MORI_AG…

• configure_sessionOverride thresholds or event modes

  Override Horizon thresholds and event modes for a specific session or, when session_id is omitted, every session YOU own (on the hosted multi-tenant server, this never touches another API key's sessions — see the tool result's 'sessions_affected' count). REQUIRES HUMAN APPROVAL — this mutates session config. Do NOT auto-run this tool. Common use cases: • Tighten clarification threshold for a customer-support domain: {session_id, clarification_threshold: 0.15} • Flip an event to active mode: {session_id, event_modes: {'alert.drift': 'active'}} • Set half-life for a long-running …

• new_conversationStart a new Horizon session

  Initialise a new Horizon conversation session. Call ONCE per distinct task or chat thread and store the returned session_id — it is required by every other tool and resource. Optionally pass metadata to set domain, user_id, or agent_name; these are embedded in trajectory reports but never sent off-device. Do NOT call for each turn — one session tracks the whole thread. To reset tracking mid-conversation, call new_conversation again and discard the old session_id.

• process_turnRecord a conversation turn

  Record one human-agent turn and return a minimal action signal. Use deferred recording: on turn 2+, call at the START of the turn with the PREVIOUS turn's human_message and agent_response (not the current turn). Turn 1: call new_conversation only — no process_turn yet. Requires an active session_id from new_conversation. Return shape: • {ok: true, turn: N} — session healthy, nothing to do • {ok: false, health_status, active_events: []} — action required When ok is false, each active_event contains: • type — e.g. 'alert.drift', 'alert.contradiction…

Signals

Stars

0

Forks

0

Open issues

0

Last commit

Sep 30, 2026 (28 days ago)

Last release

May 6, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.leocelis/horizon-fidelity-monitor

Version

0.2.1

Auth

Bearer token

License

MIT

Repository

github.com/leocelis/horizon

Website

leocelis.github.io/horizon

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql