Vivere is answering right now. Last checked 2 min ago. It exposes 37 tools.
Know when cron jobs and AI agents stop running: create monitors and check in from your agent.
Uptime history
50 days of history · worst day 96%
50 days agonow
100.0%
Uptime 24h
92 of 92 checks
37
Tools
read from the server
825 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 69
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 September 2026. No other catalogue keeps this.
2 Nov
a tool changed version6 times that day
31 Oct
a tool changed version
30 Oct
a tool changed version2 times that day
27 Oct
a tool changed version6 times that day
27 Oct
a tool changed the parameters it asks for
list_monitors
26 Oct
a tool changed version2 times that day
22 Oct
30 tools appeared
add_team_member, create_channel, create_page and 27 more
22 Oct
a tool changed version3 times that day
20 Oct
a tool changed version
18 Oct
a tool changed version2 times that day
and 30 more, back to 17 September 2026
Nothing serious here today
Today is the operative word: we check Vivere every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.
run in your terminal
claude mcp add monitors --transport http https://vivere.dev/mcpSettings → Connectors → Add custom connector, then paste this address
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
{
"servers": {
"monitors": {
"type": "http",
"url": "https://vivere.dev/mcp"
}
}
}Available tools 37
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.
delete_monitor
Delete a monitor and all its history. This cannot be undone; pause_monitor stops alerts without losing anything.
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.
list_monitor_events
One monitor's status changes (up, down, late, paused), newest first.
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.
team
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.
create_team
Make a team, on the Team plan.
delete_team
Delete a team. Its members lose the pages it gave them.
get_team
One team: its members and the pages shared with it.
remove_team_member
Take an account out of a team.
page
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.
delete_page
Delete one of your pages. Only an empty page that is not your first can go.
get_page
One page: its public address, monitors and, on your own pages, who it is shared with and as what.
update_page
Rename one of your pages or change its slug, which moves its public address.
channel
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.
delete_channel
Delete an alert channel. Monitors stop sending alerts to it.
update_channel
Rename a channel or change its settings. Settings left out keep their value.
pixel
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.
get_pixel
One pixel and its newest loads: when, from which page, browser, language and platform.
account
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.
channels
list_channels
Your alert channels. Secret settings are never shown; secrets_set names the ones that have a value.
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.
events
list_events
Status changes across the account's own monitors, newest first.
get
get_run
One run with the output it sent (the log), where it came from and what it cost.
make
make_page_private
Turn off Public on every monitor on one of your pages, which takes its public status page down.
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.
pixels
list_pixels
Your tracking pixels, with the tag to paste and how often each has loaded.
rename
rename_team
Rename a team.
resume
resume_monitor
Resume a paused monitor.
runs
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.
share
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.
teams
list_teams
Your teams, with how many members and pages each has.
test
test_channel
Send a test alert to a channel.
unshare
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://vivere.dev/mcp | streamable-http | answering | 839 ms | 2 min ago |
Alternatives to Vivere
same job, measured the same waySereno
by asksereno
A cron job monitor your AI agent sets up and can ask why a job failed. Free for up to 200 checks.
Uptimepage
by uptimepage
Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.
Orbilo
by orbilo
Check whether a website is ready for AI agents (UCP, WebMCP, Access) and monitor your own sites.
Pingcheck MCP
by churman1113
PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key.
Cronalert
by jaredhobbs
Manage CronAlert uptime monitors, check results, and incidents from any MCP client.
CronPulser
by cronpulser
Manage CronPulser from an AI agent: HTTP, Runner and TLS jobs, alerts, Runners and run history.
Exit1 Uptime Monitoring
by exit1
Set up uptime monitoring from your editor: create checks, alerts, and query uptime. Can sign you up.
StackWitness
by stackwitness
Independent monitoring: status, monitors, and incidents from your StackWitness workspace.
Vivere — questions
Answers built from our own checks of this server.
What can Vivere do?
It exposes 37 tools, read directly from the server on our last check. Among them: add_team_member, check_in, create_channel, create_monitor, create_page, create_pixel and 31 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 →
What is Vivere mostly used for?
Its tools cluster around team, monitor and page. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
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 825 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 in the form 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 37 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 825 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.