Vivere

dev.vivere/monitors

Know when cron jobs and AI agents stop running: create monitors and check in from your agent.

Yes, your AI can use this right now.Answered a live MCP handshake in 1305 ms with no sign-in needed and exposes 7 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://vivere.dev/mcp

7 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
list_pagesread-only

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.

list_monitorsread-only

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.

get_monitorread-only

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.

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.

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.

pause_monitor

Pause a monitor so it stops alerting until resumed or pinged again.

resume_monitor

Resume a paused monitor.

Alternatives in Cloud & Infra

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”