Vivere

Connect Remote server

claude mcp add --transport http monitors https://vivere.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"

{
  "mcpServers": {
    "monitors": {
      "url": "https://vivere.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

{
  "servers": {
    "monitors": {
      "type": "http",
      "url": "https://vivere.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

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

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 37 found in our last check

• 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.

• 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.

• 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.

• 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.

• get_account

  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.

• update_monitor

  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_id, to another of their own pages.

• delete_monitor

  Delete a monitor and all its history. This cannot be undone; pause_monitor stops alerts without losing anything.

• list_runs

  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.

• get_run

  One run with the output it sent (the log), where it came from and what it cost.

• list_monitor_events

  One monitor's status changes (up, down, late, paused), newest first.

• list_events

  Status changes across the account's own monitors, newest first.

• get_page

  One page: its public address, monitors and, on your own pages, who it is shared with and as what.

• create_page

  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.

• update_page

  Rename one of your pages or change its slug, which moves its public address.

• delete_page

  Delete one of your pages. Only an empty page that is not your first can go.

• make_page_private

  Turn off Public on every monitor on one of your pages, which takes its public status page down.

• share_page

  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 seat for anybody new, and the Team plan for teams.

• unshare_page

  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.

• list_teams

  Your teams, with how many members and pages each has.

• get_team

  One team: its members and the pages shared with it.

• create_team

  Make a team, on the Team plan.

• rename_team

  Rename a team.

• delete_team

  Delete a team. Its members lose the pages it gave them.

• add_team_member

  Add the account of a person with a Vivere login to a team. Joining a team that has pages takes a seat.

• remove_team_member

  Take an account out of a team.

• list_channels

  Your alert channels. Secret settings are never shown; secrets_set names the ones that have a value.

• create_channel

  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.

• update_channel

  Rename a channel or change its settings. Settings left out keep their value.

• delete_channel

  Delete an alert channel. Monitors stop sending alerts to it.

• test_channel

  Send a test alert to a channel.

• list_pixels

  Your tracking pixels, with the tag to paste and how often each has loaded.

• get_pixel

  One pixel and its newest loads: when, from which page, browser, language and platform.

• create_pixel

  Make a tracking pixel, within the plan's pixels. Returns the <img> tag to paste into a page or an email.

• delete_pixel

  Delete a pixel and every load it recorded.

Headers

Details

More ai and media servers See all

• bv7x strategy agents

  Find bv7x prediction agents on Robinhood Chain by market; quote their sealed calls, sold via x402.

• Chronary

  Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.

• Mastering

  Audio mastering for AI agents: LUFS analysis, Suno artifact cleanup, free daily master.

• Modulos AI Governance Platform

  Evaluate Modulos (EU AI Act, ISO 42001, NIST AI RMF): capabilities, trust, comparisons. Book a demo.

• naulon

  Check citations and retractions by DOI, and see the x402 price an AI agent pays to cite a source.

• NextConstraint

  Your SaaS funnel's costliest leak, its fix, watchdog alerts and verdicts, from NextConstraint.