Agents Index

Vivere

Online

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

Visit publisherConnectJSON

What it can do: 37 tools

  • list_pages read-onlyList 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_monitors read-onlyList 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_monitor read-onlyGet 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_monitorCreate 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
  • check_inReport 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_monitorPause a monitor so it stops alerting until resumed or pinged again.
  • resume_monitorResume a paused monitor.
  • get_account read-onlyWhich account this key belongs to, its 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.
  • update_monitorChange 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_id, to another of th
  • delete_monitorDelete a monitor and all its history. This cannot be undone; pause_monitor stops alerts without losing anything.
  • list_runs read-onlyA 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.
  • get_run read-onlyOne run with the output it sent (the log), where it came from and what it cost.
  • list_monitor_events read-onlyOne monitor's status changes (up, down, late, paused), newest first.
  • list_events read-onlyStatus changes across the account's own monitors, newest first.
  • get_page read-onlyOne page: its public address, monitors and, on your own pages, who it is shared with and as what.
  • create_pageAdd a page to group monitors under, within the account's limit on pages. Its slug is its public address, made from the title when not given.
  • update_pageRename one of your pages or change its slug, which moves its public address.
  • delete_pageDelete one of your pages. Only an empty page that is not your first can go.
  • make_page_privateTurn off Public on every monitor on one of your pages, which takes its public status page down.
  • share_pageShare 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 free seat for anybody new.
  • unshare_pageStop 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.
  • list_teams read-onlyYour teams, with how many members and pages each has.
  • get_team read-onlyOne team: its members and the pages shared with it.
  • create_teamMake a team.
  • rename_teamRename a team.
  • delete_teamDelete a team. Its members lose the pages it gave them.
  • add_team_memberAdd the account of a person with a Vivere login to a team. Joining a team that has pages takes a seat.
  • remove_team_memberTake an account out of a team.
  • list_channels read-onlyYour alert channels. Secret settings are never shown; secrets_set names the ones that have a value.
  • create_channelAdd an alert channel. Settings by kind: email {to}; webhook {url, secret}; slack {url}; discord {url}; telegram {token, chat_id}; ntfy {url, token}.
  • update_channelRename a channel or change its settings. Settings left out keep their value.
  • delete_channelDelete an alert channel. Monitors stop sending alerts to it.
  • test_channelSend a test alert to a channel.
  • list_pixels read-onlyYour tracking pixels, with the tag to paste and how often each has loaded.
  • get_pixel read-onlyOne pixel and its newest loads: when, from which page, browser, language and platform.
  • create_pixelMake a tracking pixel, within the account's limit on pixels. Returns the <img> tag to paste into a page or an email.
  • delete_pixelDelete a pixel and every load it recorded.

Connect it

Claude Code
claude mcp add --transport http vivere https://vivere.dev/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://vivere.dev/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "vivere": {
      "url": "https://vivere.dev/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "vivere": {
      "type": "http",
      "url": "https://vivere.dev/mcp"
    }
  }
}

Questions

What does Vivere do?

Know when cron jobs and AI agents stop running: create monitors and check in from your agent. It exposes 37 tools to AI assistants.

What tools does Vivere provide?

37 tools, including list_pages, list_monitors, get_monitor, create_monitor, check_in, pause_monitor, resume_monitor, get_account, update_monitor, delete_monitor, list_runs, get_run….

How do I connect Vivere to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://vivere.dev/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Vivere require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Vivere online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Vivere?

vivere.dev. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Cloud & DevOps