Vivere MCP Server

by vivere Your server? Claim it

answering

Vivere is answering right now. Last checked 3 min ago. It exposes 7 tools.

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

Uptime history 5 days of history · worst day 99%

5 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

946 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 September 2026. No other catalogue keeps this.

18 Sep a tool changed version2 times that day

17 Sep a tool changed version2 times that day

and 2 more, back to 17 September 2026

Vivere missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.monitors]
url = "https://vivere.dev/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

monitor

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.

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.

check

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.

monitors

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.

pages

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.

pause

pause_monitor

Pause a monitor so it stops alerting until resumed or pinged again.

resume

resume_monitor

Resume a paused monitor.

Endpoints

URL	Transport	State	Latency	Checked
https://vivere.dev/mcp	streamable-http	answering	957 ms	3 min ago

Alternatives to Vivere

same job, measured the same way

Uptimepage

by uptimepage

Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.

16 tools answering

Orbilo

by orbilo

Check whether a website is ready for AI agents (UCP, WebMCP, Access) and monitor your own sites.

5 tools answering

Pingcheck MCP

by churman1113

PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key.

56 installs/wk local only

Cronalert

by jaredhobbs

Manage CronAlert uptime monitors, check results, and incidents from any MCP client.

49 installs/wk local only

LastPing

by lastping

Monitoring that agents set up for themselves — cron jobs, CI/CD pipelines and AI agent runs.

39 tools answering

StackWitness

by stackwitness

Independent monitoring: status, monitors, and incidents from your StackWitness workspace.

answering

Deployment.io

by deployment-io

Deploy apps on your cloud. Create environments, configure infrastructure, and monitor jobs.

answering

Reqistry

by reqistry

Discover, compare, and monitor 1,400+ APIs directly from your AI coding agent.

13 tools answering

Vivere — questions

Answers built from our own checks of this server.

What can Vivere do?

It exposes 7 tools, read directly from the server on our last check. Among them: check_in, create_monitor, get_monitor, list_monitors, list_pages, pause_monitor and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Vivere working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 946 ms. The bar chart above shows every period we have measured.

How do I connect Vivere?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Vivere need an API key?

No. Vivere completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Vivere?

It answers our handshake in 946 ms on average, which is faster than 10% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.