Horizon Fidelity Monitor MCP Server

by leocelis Your server? Claim it

answering

Horizon Fidelity Monitor is answering right now. Last checked 13 min ago. Last commit 26 Oct 2026.

Tracks conversation health in real time — drift, desync, and causal collapse — for any AI agent.

Uptime history 91 days of history · worst day 96%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

647 ms

Response time

average over 24h

Stars

last commit 26 Oct 2026

What the code does

We read the source, 4 h ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command src/horizon_monitor/memento/adapters/git_local.py:52

            result = subprocess.run(  # noqa: S603 — local git binary, fixed argv, no shell

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add horizon-fidelity-monitor --transport sse https://horizon.leocelis.com/sse

Settings → Connectors → Add custom connector, then paste this address

https://horizon.leocelis.com/sse

~/.codex/config.toml

[mcp_servers.horizon-fidelity-monitor]
url = "https://horizon.leocelis.com/sse"

.cursor/mcp.json

{
  "mcpServers": {
    "horizon-fidelity-monitor": {
      "url": "https://horizon.leocelis.com/sse"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "horizon-fidelity-monitor": {
      "type": "sse",
      "url": "https://horizon.leocelis.com/sse"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://horizon.leocelis.com/sse	sse	needs auth	630 ms	13 min ago

Alternatives to Horizon Fidelity Monitor

same job, measured the same way

Uptimemonitoring

by uptimemonitoring

Agent-native uptime monitoring. Create, inspect, and assert monitor health. Free 50-monitor tier.

answering

Docker MCP Server

by friendlygeorge

MCP server for Docker — containers, health checks, Compose, logs, monitoring for AI agents

113 installs/wk local only

Infra Health & SSL Monitor MCP

by ansarii

Monitors TLS/SSL certificate expiry, DNS resolution, and TCP port status for AI agents.

answering

Uptrack MCP

by uptrack-app

MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents.

answering

Rewst MCP

by servosity

Operate and monitor Rewst RPA across every client org: automation health, failures, ROI, and drift.

local only

AWS Spapi MCP

by cesarobedfl

MCP server for Amazon SP-API - real-time inventory health, sales metrics, and price updates

81 installs/wk local only

Agent Domains

by clize

Domains your AI agent can buy, point and monitor, with four-layer health checks and alerts.

202 installs/wk local only

Synap Memory

by maximem

Persistent memory for AI agents — log and recall conversation context over MCP.

4 tools answering

Horizon Fidelity Monitor — questions

Answers built from our own checks of this server.

Why is there no tool list for Horizon Fidelity Monitor?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Horizon Fidelity Monitor working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 647 ms. The bar chart above shows every period we have measured.

How do I connect Horizon Fidelity Monitor?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Horizon Fidelity Monitor need an API key?

Yes. Every time we knock, Horizon Fidelity Monitor answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Horizon Fidelity Monitor?

It answers our handshake in 647 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Horizon Fidelity Monitor open source?

The code is open source: it is published under the MIT licence, written in Python and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at horizon.leocelis.com, which runs on its operator's own terms.