Vivere vs World Monitor
A side-by-side look at the Vivere and World Monitor 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 Vivere for monitoring work over a hosted endpoint; choose World Monitor for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
VChoose Vivere when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
Choose World Monitor when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Vivere | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 37/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 88,550 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Vivere | View World Monitor |
Tools & capabilities
Vivere tools
No tool names declared yet. Check the project README from the listing page.
World Monitor 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.
Vivere
{
"mcpServers": {
"vivere": {
"url": "https://vivere.dev/docs/mcp"
}
}
}
World Monitor
{
"mcpServers": {
"world-monitor": {
"command": "npx",
"args": [
"-y",
"worldmonitor"
]
}
}
}
Frequently asked questions
Vivere is categorized under Monitoring and uses a remote HTTP/SSE transport. World Monitor belongs to Monitoring and uses a local stdio subprocess. Pick Vivere for monitoring work and World Monitor 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.
Vivere has no declared pricing — check the project's own site. World Monitor is listed as free. Auth: other. 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 vivere and world-monitor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vivere has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. World Monitor has 55/100 (Good) with 5 views, 0 installs and 88,550 GitHub stars.
