Horizon Fidelity Monitor vs Vivere
A side-by-side look at the Horizon Fidelity Monitor and Vivere MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
V
VivereMonitoring · Remote HTTP/SSEKnow when cron jobs and AI agents stop running: create monitors and check in from your agent.37FairAuth: not declaredVerdict: choose Horizon Fidelity Monitor for monitoring work as a local process; choose Vivere for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Horizon Fidelity Monitor when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
VChoose Vivere when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Vivere | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 40/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Horizon Fidelity Monitor | View Vivere |
Tools & capabilities
Horizon Fidelity Monitor tools
No tool names declared yet. Check the project README from the listing page.
Vivere tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Horizon Fidelity Monitor
{
"mcpServers": {
"horizon-fidelity-monitor": {
"command": "uvx",
"args": [
"horizon-monitor"
]
}
}
}
Vivere
{
"mcpServers": {
"vivere": {
"url": "https://vivere.dev/docs/mcp"
}
}
}
Frequently asked questions
Horizon Fidelity Monitor is categorized under Monitoring and uses a local stdio subprocess. Vivere belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Horizon Fidelity Monitor for monitoring work and Vivere for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Horizon Fidelity Monitor has no declared pricing — check the project's own site. Vivere has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add horizon-fidelity-monitor and vivere as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Horizon Fidelity Monitor has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Vivere has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
