Horizon Fidelity Monitor MCP Server
io.github.leocelis/horizon-fidelity-monitor
answering
Horizon Fidelity Monitor is answering right now. Last checked 8 min ago. Last commit 19 Jul 2026.
Tracks conversation health in real time — drift, desync, and causal collapse — for any AI agent.
Uptime history
39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
631 ms
Response time
average over 24h
0
Stars
last commit 19 Jul 2026
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.
run in your terminal
claude mcp add horizon-fidelity-monitor --transport http https://horizon.leocelis.com/sse~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"horizon-fidelity-monitor": {
"url": "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
{
"mcpServers": {
"horizon-fidelity-monitor": {
"url": "https://horizon.leocelis.com/sse"
}
}
}This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://horizon.leocelis.com/sse | sse | needs key | 692 ms | 8 min ago |
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 631 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 with the file path 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 key or an OAuth login: 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 631 ms on average, which is faster than 14% 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?
Yes — it is published under the MIT licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.