Horizon Fidelity Monitor MCP server
online · 100% uptimeio.github.leocelis/horizon-fidelity-monitor·v0.2.1Tracks conversation health in real time — drift, desync, and causal collapse — for any AI agent.
0 stars
Reviews
Write oneNobody has reviewed Horizon Fidelity Monitor yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Horizon Fidelity Monitor tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 364ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityauth enforced (unknown)9/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Horizon Fidelity Monitor compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 87/100
- higher than 78% of 4,460 AI and agents servers
- Uptime
- 100%
- of our recent checks; the typical remote AI and agents server answers 100%
- Response time
- 491 ms
- faster than 27% of 2,331 AI and agents servers
Install Horizon Fidelity Monitor in Claude Code, Cursor or VS Code
claude mcp add --transport http horizon-fidelity-monitor https://horizon.leocelis.com/sse
What the publisher says
From the Horizon Fidelity Monitor repository's README, as published. We do not edit it. Read it on GitHub
Horizon Fidelity Monitor
"Quality is not a model property — it is a conversation property."
Horizon is a real-time conversation health monitor for AI agents. It tracks the structural dynamics of multi-turn conversations — semantic drift, information gain, ontological gap width, temporal desynchronisation, circadian cognitive load, conversation velocity, and causal reachability — dimensions that LLMs do not reliably surface from inside the conversation.
Horizon ships two measurement planes. The conversation plane (above, always present) measures the health of a dialogue turn by turn. The optional mission plane — Memento Mori — measures elapsed calendar time against goals: ages, deadlines, stalls, per-entity latency, and share of a finite horizon. It is inert until you configure a store. See Mission plane.
Horizon is not a manipulation, sycophancy, or human-influence detector — it measures conversation dynamics, not whether an agent is steering or flattering the user. See LEGAL.md §1.
Why an external monitor? LLMs have limited and unreliable self-knowledge: introspection research shows partial self-access that is brittle and degrades on complex or out-of-distribution tasks (Binder et al. 2024; arXiv:2512.12411). So rather than depend on a model reporting its own conversation dynamics, Horizon measures them externally with cheap, deterministic, always-on arithmetic that does not call the model at all.
Why this exists
Multi-turn AI agents lose accuracy. The ICLR 2026 Outstanding Paper "LLMs Get Lost In Multi-Turn Conversation" (Laban, Hayashi, Zhou & Neville — Microsoft Research / Salesforce Research) reports 39% average accuracy degradation across multi-turn evaluation — a structural property that standard observability tools (LangSmith, RAGAS, DeepEval) cannot see because they measure responses, not conversations.
Horizon was built to close that gap. It is observability first: it surfaces conversation dynamics that response-level tools miss, using cheap deterministic arithmetic with zero model calls. In four controlled A/B scenarios where Horizon events drove a re-grounding intervention we measured a +15.7% composite quality lift and 87% fewer hallucination events — but those are synthetic, scripted scenarios with a hand-tuned controller, not a production result. Treat them as promising in-house evidence, not a guaranteed outcome (see Validation and LEGAL.md §5). Every signal — information gain, divergence, estimated ontological gap width, causal reachability — is a standard information-theory or arithmetic measure computed on text embeddings and timestamps; see 4D Spacetime Signals for the full definitions.
- Read the demand proof → ICLR 2026 Outstanding Paper (Laban et al.)
- Read the category argument → docs/content/naming-the-category-conversation-dynamics-monitoring.md
- Read the engineering case → docs/content/why-every-production-agent-needs-conversation-dynamics-monitoring.md
Getting started
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Horizon Fidelity Monitor: common questions
- Is Horizon Fidelity Monitor MCP server safe?
- Yes, by our scan: it is graded A (87/100). Read the Horizon Fidelity Monitor safety report
- How do I install Horizon Fidelity Monitor?
- It runs remotely at horizon.leocelis.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Horizon Fidelity Monitor need an API key?
- Yes. The registry entry asks for
Authorization. - Is Horizon Fidelity Monitor maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v0.2.1.
- Is Horizon Fidelity Monitor up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Horizon Fidelity Monitor?
- Servers from other publishers that do the same job: Emilia Protocol MCP server, Agent Recall MCP server and Skillsmith MCP server.
- How does Horizon Fidelity Monitor compare with other AI and agents MCP servers?
- safety score 87/100 (higher than 78% of 4,460 AI and agents servers); uptime 100% (of our recent checks; the typical remote AI and agents server answers 100%); response time 491 ms (faster than 27% of 2,331 AI and agents servers). Full comparison.
Alternatives to Horizon Fidelity Monitor
Same job from other publishers: the closest match first, then the best rated.
- Emilia ProtocolExact-action approval for consequential agent actions: request, track, and verify signed receipts.not reviewedEstablishedB
- Agent RecallCorrection-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.not reviewedEstablishedA
- SkillsmithShare agent skills across your team, scan them for risk, and track what's actually used.not reviewedEstablishedB