Connect Vivere and your agent gets 7 tools, among them check_in, create_monitor, get_monitor. It answers at https://vivere.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 5 of 5 times since 13 September 2026; the last check, on 19 October 2026, succeeded.
Know when cron jobs and AI agents stop running: create monitors and check in from your agent.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
check_in | Report on a heartbeat monitor: 'success' after a completed run (resets the deadline), 'start' when a run begins, 'fail' when it failed. Include a short message; it is kept as the run log. Inputs: message, monitor_id, status |
create_monitor | Create a heartbeat monitor (default) or an HTTP check on the account's first page or on page_id, which may be a page shared with this account as editor. Returns the monitor and, for heartbeats, the ping URL to call after each run. Inputs: cron, grace, interval, kind, name, page_id |
get_monitor | Get one monitor by id, including its ping URL for heartbeat monitors, or by page_id and slug, which also works on a page shared to view. Inputs: id, page_id, slug |
list_monitors | List the monitors on every page this account can see, or on one page, with status, page and access. Monitors on a page shared to view have no id; address them by page_id and slug. Inputs: page_id |
list_pages | List the pages this account can see: its own, then pages other accounts share with it, each with the access it has there (owner, editor or viewer) and how many monitors are on it and down. |
pause_monitor | Pause a monitor so it stops alerting until resumed or pinged again. Inputs: id |
resume_monitor | Resume a paused monitor. Inputs: id |
Every block below points at https://vivere.dev/mcp. Pick your client and copy.
claude mcp add --transport http vivere https://vivere.dev/mcp
{
"mcpServers": {
"vivere": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://vivere.dev/mcp"]
}
}
}{
"mcpServers": {
"vivere": {
"url": "https://vivere.dev/mcp"
}
}
}{
"servers": {
"vivere": {
"type": "http",
"url": "https://vivere.dev/mcp"
}
}
}{
"context_servers": {
"vivere": {
"url": "https://vivere.dev/mcp"
}
}
}{
"mcpServers": {
"vivere": {
"serverUrl": "https://vivere.dev/mcp"
}
}
}{
"mcpServers": {
"vivere": {
"url": "https://vivere.dev/mcp"
}
}
}name: Vivere
version: 0.0.1
schema: v1
mcpServers:
- name: Vivere
type: streamable-http
url: https://vivere.dev/mcp{
"mcpServers": {
"vivere": {
"httpUrl": "https://vivere.dev/mcp"
}
}
}{
"mcpServers": {
"vivere": {
"type": "http",
"url": "https://vivere.dev/mcp"
}
}
}{
"mcpServers": {
"vivere": {
"url": "https://vivere.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fvivere.dev%2Fmcp&type=streamable_http&id=vivere&name=Vivere
It answered our last check on 19 October 2026 in 790 ms. Over 5 checks since 13 September 2026 it answered 5. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by vivere.dev and served from vivere.dev, the vendor's own domain: https://vivere.dev/mcp.
7, as returned by the server's own tools/list on 24 September 2026: check_in, create_monitor, get_monitor, list_monitors, list_pages, pause_monitor, resume_monitor.
It answered our last check on 19 October 2026 in 790 ms. Over 5 checks since 13 September 2026 it answered 5.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://vivere.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.vivere. Endpoint host: vivere.dev. ARD identifier: urn:air:dev.vivere:mcp:monitors.
First indexed 13 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.