Vivere
dev.vivere/monitorsKnow when cron jobs and AI agents stop running: create monitors and check in from your agent.
Score: 100/100
Handshake verified by our own probe.
Tools · 37
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 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 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 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 pi…
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 a monitor so it stops alerting until resumed or pinged again.
Resume a paused monitor.
Which account this key belongs to, its plan's limits and what it uses of them, and what this key may do: its permission on each resource (none, read or write) and the pages it is limited to, if any.
Change a monitor. Only the fields given change; its kind cannot. Setting cron switches a heartbeat to a cron schedule and setting period switches it back. Only the page's owner can move it, with page_…
Delete a monitor and all its history. This cannot be undone; pause_monitor stops alerts without losing anything.
A heartbeat monitor's newest runs with their outcome, duration, exit code and any model, tokens and cost they reported, plus what its runs cost over 30 days.
One run with the output it sent (the log), where it came from and what it cost.
One monitor's status changes (up, down, late, paused), newest first.
Status changes across the account's own monitors, newest first.
One page: its public address, monitors and, on your own pages, who it is shared with and as what.
Add a page to group monitors under, within the plan's pages. Its slug is its public address, made from the title when not given.
Rename one of your pages or change its slug, which moves its public address.
Delete one of your pages. Only an empty page that is not your first can go.
Turn off Public on every monitor on one of your pages, which takes its public status page down.
Share one of your pages with the account of a person who has a Vivere login (email) or with one of your teams (team_id), as viewer or editor, or change the role they have. Needs a paid plan, a free se…
Stop sharing one of your pages with an account (account_id, from get_page) or a team (team_id). Their alert channels come off its monitors.
Your teams, with how many members and pages each has.
One team: its members and the pages shared with it.
Make a team, on the Team plan.
Rename a team.
Delete a team. Its members lose the pages it gave them.
Add the account of a person with a Vivere login to a team. Joining a team that has pages takes a seat.
Take an account out of a team.
Your alert channels. Secret settings are never shown; secrets_set names the ones that have a value.
Add an alert channel. Settings by kind: email {to}; webhook {url, secret}; slack {url}; discord {url}; telegram {token, chat_id}; ntfy {url, token}. Slack, Discord, Telegram and ntfy need a paid plan.
Rename a channel or change its settings. Settings left out keep their value.
Delete an alert channel. Monitors stop sending alerts to it.
Send a test alert to a channel.
Your tracking pixels, with the tag to paste and how often each has loaded.
One pixel and its newest loads: when, from which page, browser, language and platform.
Make a tracking pixel, within the plan's pixels. Returns the <img> tag to paste into a page or an email.
Delete a pixel and every load it recorded.
How to use
Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://vivere.dev/mcp
Cursor or Cline: add to your MCP config:
{
"mcpServers": {
"vivere": {
"url": "https://vivere.dev/mcp",
"transport": "streamable-http"
}
}
}