Vivere

by vivere.dev · dev.vivere/monitors

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

OnlineRemote
Category
AI and agents
Connection
Remote (HTTP)
Tools
37 reported
Status
Online

Connect it to your AI

Claude Code

claude mcp add --transport http monitors https://vivere.dev/mcp

Claude, ChatGPT, Cursor and other apps

Add it as a custom connector with this URL (Streamable HTTP):

https://vivere.dev/mcp

This server expects extra headers, usually an API key from its maker.

Cursor, VS Code and other apps (mcp.json)

{
  "mcpServers": {
    "monitors": {
      "url": "https://vivere.dev/mcp"
    }
  }
}

Tools it offers

37 tools, as the server itself reported during our check on Oct 31, 2026.

  • list_pagesList 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_monitorsList 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_monitorGet 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_accountWhich 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.
  • 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_runsA 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_runOne run with the output it sent (the log), where it came from and what it cost.
  • list_monitor_eventsOne monitor's status changes (up, down, late, paused), newest first.
  • list_eventsStatus changes across the account's own monitors, newest first.
  • get_pageOne 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 plan's 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 paid plan, 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_teamsYour teams, with how many members and pages each has.
  • get_teamOne team: its members and the pages shared with it.
  • create_teamMake a team, on the Team plan.
  • 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_channelsYour 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}. Slack, Discord, Telegram and ntfy need a paid plan.
  • 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_pixelsYour tracking pixels, with the tag to paste and how often each has loaded.
  • get_pixelOne pixel and its newest loads: when, from which page, browser, language and platform.
  • create_pixelMake a tracking pixel, within the plan's pixels. Returns the <img> tag to paste into a page or an email.
  • delete_pixelDelete a pixel and every load it recorded.

Questions

What is the Vivere MCP server?

Know when cron jobs and AI agents stop running: create monitors and check in from your agent. It is made by vivere.dev and listed in the official MCP Registry as dev.vivere/monitors. MCP (Model Context Protocol) is the open standard that lets AI apps like Claude, ChatGPT and Cursor use outside tools.

How do I add Vivere to Claude?

In the Claude app or claude.ai, open Settings, then Connectors, choose "Add custom connector" and paste https://vivere.dev/mcp. In Claude Code, run: claude mcp add --transport http monitors https://vivere.dev/mcp

How do I add Vivere to ChatGPT?

ChatGPT can use remote MCP servers as connectors. In ChatGPT settings, under Apps and Connectors, turn on developer mode if asked, create a new connector and paste https://vivere.dev/mcp.

How do I add Vivere to Cursor?

Open Cursor settings, go to MCP, choose "Add new MCP server" (or edit ~/.cursor/mcp.json) and add: { "mcpServers": { "monitors": { "url": "https://vivere.dev/mcp" } } }

Does Vivere work right now?

Yes. It responded when we last checked on 31 Oct 2026. We check remote MCP servers every day.

What can Vivere do?

It gives your AI 37 tools, including list_pages, list_monitors, get_monitor, create_monitor, check_in. The full list is on this page.

Is this your server? Get the badge for your README
chen.media/mcp badge

Markdown (GitHub README)

[![Listed on chen.media/mcp](https://chen.media/mcp/badge/dev-vivere-monitors.svg)](https://chen.media/mcp/dev-vivere-monitors)

HTML (switches to dark mode on its own)

<a href="https://chen.media/mcp/dev-vivere-monitors"><picture><source media="(prefers-color-scheme: dark)" srcset="https://chen.media/mcp/badge/dev-vivere-monitors.svg?theme=dark"><img src="https://chen.media/mcp/badge/dev-vivere-monitors.svg" alt="Listed on chen.media/mcp" height="40"></picture></a>

More in AI and agents

See all