Developer · Remote MCP server
Vivere
Know when cron jobs and AI agents stop running: create monitors and check in from your agent.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.vivere/monitors- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-13
- Updated
- 2026-09-13
- Publisher
- dev.vivere
- Namespace
- Namespace verified by the MCP Registry via the domain vivere.dev · how
- Website
- vivere.dev/docs/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://vivere.dev/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- vivere c0f40d1 · protocol 2025-06-18
- Tools discovered
- 7:
list_pages,list_monitors,get_monitor,create_monitor,check_in,pause_monitor,resume_monitor - Checked on
- 2026-10-05
How to connect Vivere
Vivere is a remote MCP server: there is nothing to install. Its endpoint is https://vivere.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Virtual FilesystemPostgreSQL-backed virtual filesystem for agents: session isolation, shared stores, POSIX ops, RLS. | Local · stdio |
| Visily UI DesignUI design from prompts, screenshots, and URLs for AI coding agents and theme tokens. | Remote · HTTPLive check: sign-in required |
| vivacProvenance tree for coding agents: where you are, why, and what was already decided. | Local · stdio |
| Vivado MCP NativeNative MCP server for controlling AMD/Xilinx Vivado on Windows and Linux via persistent Tcl. | Local · stdio |
| ViviooTrust infrastructure for AI agents. Directory, jobs, verification, and 360 feedback. | Remote · SSELive check: ✓ SSE reachable |
| vivioo.ioTrust infrastructure for AI agents. Directory, jobs, verification, and 360 feedback. | Remote · SSELive check: ✓ SSE reachable |
| Vizier GuardDeterministic authorization and security guard for AI agent actions with signed receipts. | Local · stdio |
| VMware AIopsAI-powered VMware vCenter/ESXi VM lifecycle and deployment with 60 MCP tools. | Local · stdio |