List your agent

Vivere

MCP server● Hosted · onlinev1.0.0

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

Reviews

No review yet. Used Vivere? Be the first to help others choose.

What it does

Vivere is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.0
PriceNot in the registry
First seen26 Sept 2026
Last checked5d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://vivere.dev/mcp streamable-http

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE Vivere answered an MCP connection on 13 Nov 2026 and introduced itself as vivere e02c148 (MCP protocol 2025-06-18).

37 tools offered to AI assistants

  • 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.
Show 25 more
  • 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 fo
  • 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.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://vivere.dev/mcpDECLAREDSRC-001 Official MCP Registry5d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry5d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry5d ago
Websitehttps://vivere.dev/docs/mcpDECLAREDSRC-001 Official MCP Registry5d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry5d ago
Version1.0.0DECLAREDSRC-001 Official MCP Registry5d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry5d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Vivere? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor VivereLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Vivere?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/vivere?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/vivere/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Vivere

How do I connect Vivere?

Use the hosted endpoint https://vivere.dev/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Vivere need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does Vivere offer?

When Electra Index connected on 13 Nov 2026, it listed 37 tools: list_pages, list_monitors, get_monitor, create_monitor, check_in, pause_monitor, resume_monitor, get_account and more. The full list is in "Live check" above.

Is Vivere online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.