Skip to content

Vivere MCP server

dev.vivere/monitorsvivere.devstreamable-httpv1.0.0Scanned

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

37 tools: 6 can delete or cancel things, 1 do something that can't be undone, 16 change things and 14 only read.

Tools: 6 delete, 1 irreversible, 16 write, 14 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 4
  • 1 finding

Tools listed without sign-in. Remote posture

Anlyon alternative

23 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Vivere MCP server can do

The Vivere MCP server is published by vivere.dev, a domain the MCP Registry verified. It has 37 tools. It can delete or cancel things (6 tools: delete_monitor, delete_page, delete_team, remove_team_member and 2 more), do things that cannot be undone, such as sending, paying or publishing (test_channel) and create or change data (16 tools: create_monitor, check_in, pause_monitor, resume_monitor and 12 more). 14 tools only read.

2 tools bring in text other people can write (get_monitor and get_pixel); 4 tools can send data out of your system (create_monitor, update_monitor, update_channel and 1 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

37 tools

Deletes or cancels 6Claude Code: deny
  • delete_channelDelete an alert channel.No findings

    Why it is in this group

    • The name "delete_channel" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete an alert channel. Monitors stop sending alerts to it.

    Annotations the server declares

    • title: Delete alert channel
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_monitorDelete a monitor and all its history.No findings

    Why it is in this group

    • The name "delete_monitor" says "delete": a word for removing or ending something.
    • The description says "cannot be undone".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a monitor and all its history. This cannot be undone; pause_monitor stops alerts without losing anything.

    Annotations the server declares

    • title: Delete monitor
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_pageDelete one of your pages.No findings

    Why it is in this group

    • The name "delete_page" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete one of your pages. Only an empty page that is not your first can go.

    Annotations the server declares

    • title: Delete page
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_pixelDelete a pixel and every load it recorded.No findings

    Why it is in this group

    • The name "delete_pixel" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a pixel and every load it recorded.

    Annotations the server declares

    • title: Delete pixel
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_teamDelete a team.No findings

    Why it is in this group

    • The name "delete_team" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a team. Its members lose the pages it gave them.

    Annotations the server declares

    • title: Delete team
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • remove_team_memberTake an account out of a team.1 finding

    Why it is in this group

    • The name "remove_team_member" says "remove": a word for removing or ending something.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "remove_team_member" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "remove_team_member" says "remove": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    Take an account out of a team.

    Annotations the server declares

    • title: Remove team member
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • test_channelSend a test alert to a channel.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.channel_id): what the tool writes goes there.
    Description, as the server wrote it
    Send a test alert to a channel.

    Annotations the server declares

    • title: Test alert channel
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 16Claude Code: ask
  • add_team_memberAdd the account of a person with a Vivere login to a team.No findings

    Why it is in this group

    • The name "add_team_member" says "add": a word for a change.
    Description, as the server wrote it
    Add the account of a person with a Vivere login to a team. Joining a team that has pages takes a seat.

    Annotations the server declares

    • title: Add team member
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_inReport on a heartbeat monitor: 'success' after a completed run (resets the deadline), 'start' when a run begins, 'fail' when it failed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check in
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_channelAdd an alert channel.No findings

    Why it is in this group

    • The name "create_channel" says "create": a word for a change.
    Description, as the server wrote it
    Add an alert channel. Settings by kind: email {to}; webhook {url, secret}; slack {url}; discord {url}; telegram {token, chat_id}; ntfy {url, token}.

    Annotations the server declares

    • title: Create alert channel
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • 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.Can send data outNo findings

    Why it is in this group

    • The name "create_monitor" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create monitor
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_pageAdd a page to group monitors under, within the account's limit on pages.No findings

    Why it is in this group

    • The name "create_page" says "create": a word for a change.
    Description, as the server wrote it
    Add a page to group monitors under, within the account's limit on pages. Its slug is its public address, made from the title when not given.

    Annotations the server declares

    • title: Create page
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_pixelMake a tracking pixel, within the account's limit on pixels.No findings

    Why it is in this group

    • The name "create_pixel" says "create": a word for a change.
    Description, as the server wrote it
    Make a tracking pixel, within the account's limit on pixels. Returns the <img> tag to paste into a page or an email.

    Annotations the server declares

    • title: Create pixel
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_teamMake a team.No findings

    Why it is in this group

    • The name "create_team" says "create": a word for a change.
    Description, as the server wrote it
    Make a team.

    Annotations the server declares

    • title: Create team
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • make_page_privateTurn off Public on every monitor on one of your pages, which takes its public status page down.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Turn off Public on every monitor on one of your pages, which takes its public status page down.

    Annotations the server declares

    • title: Make page private
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • pause_monitorPause a monitor so it stops alerting until resumed or pinged again.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Pause a monitor so it stops alerting until resumed or pinged again.

    Annotations the server declares

    • title: Pause monitor
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • rename_teamRename a team.No findings

    Why it is in this group

    • The name "rename_team" says "rename": a word for a change.
    Description, as the server wrote it
    Rename a team.

    Annotations the server declares

    • title: Rename team
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • resume_monitorResume a paused monitor.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Resume a paused monitor.

    Annotations the server declares

    • title: Resume monitor
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 free seat for anybody new.

    Annotations the server declares

    • title: Share page
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • unshare_pageStop sharing one of your pages with an account (account_id, from get_page) or a team (team_id).No findings

    Why it is in this group

    • The description's first verb is "stop": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Unshare page
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • update_channelRename a channel or change its settings.Can send data outNo findings

    Why it is in this group

    • The name "update_channel" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.channel_id): what the tool writes goes there.
    Description, as the server wrote it
    Rename a channel or change its settings. Settings left out keep their value.

    Annotations the server declares

    • title: Update alert channel
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • update_monitorChange a monitor.Can send data outNo findings

    Why it is in this group

    • The name "update_monitor" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.channels): what the tool writes goes there.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update monitor
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • update_pageRename one of your pages or change its slug, which moves its public address.No findings

    Why it is in this group

    • The name "update_page" says "update": a word for a change.
    Description, as the server wrote it
    Rename one of your pages or change its slug, which moves its public address.

    Annotations the server declares

    • title: Update page
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 14Show 14 read-only tools
  • get_accountWhich account this key belongs to, its 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 …No findings

    Why it is in this group

    • The name "get_account" says "get": a word for reading.
    Description, as the server wrote it
    Which account this key belongs to, its 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.

    Annotations the server declares

    • title: Get account
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_monitor" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get monitor
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_pageOne page: its public address, monitors and, on your own pages, who it is shared with and as what.No findings

    Why it is in this group

    • The name "get_page" says "get": a word for reading.
    Description, as the server wrote it
    One page: its public address, monitors and, on your own pages, who it is shared with and as what.

    Annotations the server declares

    • title: Get page
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_pixelOne pixel and its newest loads: when, from which page, browser, language and platform.Reads text others writeNo findings

    Why it is in this group

    • The name "get_pixel" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browser": it reads web pages, which anyone can write.
    Description, as the server wrote it
    One pixel and its newest loads: when, from which page, browser, language and platform.

    Annotations the server declares

    • title: Get pixel
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_runOne run with the output it sent (the log), where it came from and what it cost.No findings

    Why it is in this group

    • The name "get_run" says "get": a word for reading.
    Description, as the server wrote it
    One run with the output it sent (the log), where it came from and what it cost.

    Annotations the server declares

    • title: Get run
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_teamOne team: its members and the pages shared with it.No findings

    Why it is in this group

    • The name "get_team" says "get": a word for reading.
    Description, as the server wrote it
    One team: its members and the pages shared with it.

    Annotations the server declares

    • title: Get team
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_channelsYour alert channels.No findings

    Why it is in this group

    • The name "list_channels" says "list": a word for reading.
    Description, as the server wrote it
    Your alert channels. Secret settings are never shown; secrets_set names the ones that have a value.

    Annotations the server declares

    • title: List alert channels
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_eventsStatus changes across the account's own monitors, newest first.No findings

    Why it is in this group

    • The name "list_events" says "list": a word for reading.
    Description, as the server wrote it
    Status changes across the account's own monitors, newest first.

    Annotations the server declares

    • title: List events
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_monitor_eventsOne monitor's status changes (up, down, late, paused), newest first.No findings

    Why it is in this group

    • The name "list_monitor_events" says "list": a word for reading.
    Description, as the server wrote it
    One monitor's status changes (up, down, late, paused), newest first.

    Annotations the server declares

    • title: List monitor events
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_monitorsList the monitors on every page this account can see, or on one page, with status, page and access.No findings

    Why it is in this group

    • The name "list_monitors" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List monitors
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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 a…No findings

    Why it is in this group

    • The name "list_pages" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List pages
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_pixelsYour tracking pixels, with the tag to paste and how often each has loaded.No findings

    Why it is in this group

    • The name "list_pixels" says "list": a word for reading.
    Description, as the server wrote it
    Your tracking pixels, with the tag to paste and how often each has loaded.

    Annotations the server declares

    • title: List pixels
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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.No findings

    Why it is in this group

    • The name "list_runs" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List runs
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_teamsYour teams, with how many members and pages each has.No findings

    Why it is in this group

    • The name "list_teams" says "list": a word for reading.
    Description, as the server wrote it
    Your teams, with how many members and pages each has.

    Annotations the server declares

    • title: List teams
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out4
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
23
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://vivere.dev/.well-known/oauth-protected-resource/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 23 tools that change things (6 destructive, 1 irreversible, 16 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://vivere.dev/mcp: tools/list returned 37 tools to an anonymous client, including delete_monitor (destructive), delete_page (destructive), delete_team (destructive), remove_team_member (destructive), delete_channel (destructive) and 18 more

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 4 to 23

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "remove_team_member" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "remove_team_member" says "remove": a word for removing or ending something.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools6 changed.~6 changedView diff
  2. Tools30 added, 1 changed.+30 added~1 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 23.View diff
    • Tools that change things, listed without credentials: 4 to 23

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http monitors https://vivere.dev/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http monitors https://vivere.dev/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__monitors__list_pages",
      "mcp__monitors__list_monitors",
      "mcp__monitors__get_monitor",
      "mcp__monitors__get_account",
      "mcp__monitors__list_runs",
      "mcp__monitors__get_run",
      "mcp__monitors__list_monitor_events",
      "mcp__monitors__list_events",
      "mcp__monitors__get_page",
      "mcp__monitors__list_teams",
      "mcp__monitors__get_team",
      "mcp__monitors__list_channels",
      "mcp__monitors__list_pixels",
      "mcp__monitors__get_pixel"
    ],
    "ask": [
      "mcp__monitors__create_monitor",
      "mcp__monitors__check_in",
      "mcp__monitors__pause_monitor",
      "mcp__monitors__resume_monitor",
      "mcp__monitors__update_monitor",
      "mcp__monitors__create_page",
      "mcp__monitors__update_page",
      "mcp__monitors__make_page_private",
      "mcp__monitors__share_page",
      "mcp__monitors__unshare_page",
      "mcp__monitors__create_team",
      "mcp__monitors__rename_team",
      "mcp__monitors__add_team_member",
      "mcp__monitors__create_channel",
      "mcp__monitors__update_channel",
      "mcp__monitors__test_channel",
      "mcp__monitors__create_pixel"
    ],
    "deny": [
      "mcp__monitors__delete_monitor",
      "mcp__monitors__delete_page",
      "mcp__monitors__delete_team",
      "mcp__monitors__remove_team_member",
      "mcp__monitors__delete_channel",
      "mcp__monitors__delete_pixel"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as monitors. Review it before you use it.

Capability tags behind 6 rules
  • mcp__monitors__get_monitor untrusted-input
  • mcp__monitors__create_monitor outbound
  • mcp__monitors__update_monitor outbound
  • mcp__monitors__update_channel outbound
  • mcp__monitors__test_channel outbound
  • mcp__monitors__get_pixel untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.vivere/monitors/verify?hash=ae6d32fc809199c9ce2de1a022a95c97dc1ff6b6ae0e26cab1a1b101cb964ea9" | jq -e '.changed == false'

Pinned hash ae6d32fc8091, from Nov 15, 2026, 04:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.vivere/monitors/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.vivere/monitors
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.vivere/monitors.svg)](https://radar.anlyon.com/servers/dev.vivere/monitors)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

Vivere MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Vivere MCP server safe?

No scan can promise that. What its definitions show: 37 tools, 23 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Vivere MCP server delete data?

Yes. 6 tools can delete, cancel or revoke something: delete_monitor, delete_page, delete_team, remove_team_member, delete_channel and delete_pixel.

Can the Vivere MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: test_channel.

What tools does the Vivere MCP server have?

37 tools: 6 destructive, 1 irreversible, 16 write, 14 read. delete_monitor, delete_page, delete_team, remove_team_member, delete_channel, delete_pixel, test_channel, create_monitor and 29 more.

Does the Vivere MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Vivere MCP server send data to outside services?

4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_monitor, update_monitor, update_channel and test_channel.

Has the Vivere MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.