Vivere
REMOTE · VIVERE.DEV · SCANNED SEP 23
Know when cron jobs and AI agents stop running: create monitors and check in from your agent.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 760 tokens (~108/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Vivere MCP server?
Vivere is a hosted endpoint at https://vivere.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · vivere.dev
claude mcp add --transport http dev-vivere-monitors 'https://vivere.dev/mcp'
{
"mcpServers": {
"dev-vivere-monitors": {
"url": "https://vivere.dev/mcp"
}
}
} {
"servers": {
"dev-vivere-monitors": {
"type": "http",
"url": "https://vivere.dev/mcp"
}
}
} [mcp_servers.dev-vivere-monitors] url = "https://vivere.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-vivere-monitors": {
"type": "remote",
"url": "https://vivere.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-vivere-monitors --url 'https://vivere.dev/mcp' --transport streamable-http
mcp_servers:
dev-vivere-monitors:
url: "https://vivere.dev/mcp" {
"McpServers": {
"dev-vivere-monitors": {
"Transport": "http",
"Url": "https://vivere.dev/mcp"
}
}
} assistant mcp add dev-vivere-monitors -t streamable-http -u 'https://vivere.dev/mcp'
{
"mcpServers": {
"dev-vivere-monitors": {
"type": "http",
"url": "https://vivere.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
- Server version: 676d51c → 8ce479a functional
- 20 Sept 26 0
- Server version: 79f381c → 676d51c functional
- 19 Sept 26 +1
- Server version: dd64554 → 79f381c functional
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 82389ad → dd64554 functional
- 17 Sept 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 13 Sept 26 36
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Sept 2026 · Probed https://vivere.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vivere.dev | CN=YE1,O=Let's Encrypt,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6c43218e01887663a57443116c3438a0bdb |
| SANs: *.vivere.dev, vivere.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vivere.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| vivere.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="vivere", resource_metadata="https://vivere.dev/.well-known/oauth-protected-resource/mcp"
Bearer realm="vivere", resource_metadata="https://vivere.dev/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com; connect-src 'self'; frame-src https://challenges.cloudflare.com; frame-ancestors 'self'; form-action 'self' https://polar.sh https://*.polar.sh https://github.com https://accounts.google.com; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://vivere.dev/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Problem | metadata_incomplete |
| Resource | https://vivere.dev/mcp |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vivere.dev/mcp | Verified | 200 | |
| http (plaintext) | http://vivere.dev/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_in Check in ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | Optional summary or error text to store with the run |
| monitor_id | string | yes | Monitor id (the last path segment of the ping URL) |
| status | string | – | Default success |
No output schema declared.
No examples provided.
create_monitor Create monitor ~294
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cron | string | – | Heartbeat alternative to period: five-field cron expression, e.g. '0 2 * * *'. |
| grace | string | – | Heartbeat: how late a check-in may be before alerting, e.g. 15m. Default 15m. |
| interval | string | – | HTTP check: how often to request it, e.g. 5m. |
| kind | string | – | heartbeat (the job pings us) or http (we request a URL) |
| name | string | yes | Human name, e.g. 'nightly report agent' |
| page_id | integer | – | Page to put it on (from list_pages). Default: the account's first page. |
| period | string | – | Heartbeat: expected time between successful check-ins, e.g. 30m, 1h, 1d. Default 1h. |
| tags | string | – | Optional space-separated tags. |
| timezone | string | – | IANA timezone for the cron expression, e.g. Asia/Seoul. Default UTC. |
| url | string | – | HTTP check: the public URL to request. |
No output schema declared.
No examples provided.
get_monitor Get monitor ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Monitor id, for monitors this account owns or edits |
| page_id | integer | – | Page id, with slug |
| slug | string | – | Monitor slug, with page_id |
No output schema declared.
No examples provided.
list_monitors List monitors ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | integer | – | Only this page (from list_pages) |
No output schema declared.
No examples provided.
list_pages List pages ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pause_monitor Pause monitor ~32
Pause a monitor so it stops alerting until resumed or pinged again.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor id |
No output schema declared.
No examples provided.
resume_monitor Resume monitor ~22
Resume a paused monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor id |
No output schema declared.
No examples provided.
What is the Vivere MCP server?
Vivere is an MCP server listed in the public MCP registry as dev.vivere/monitors. Know when cron jobs and AI agents stop running: create monitors and check in from your agent. This page covers its hosted endpoint (https://vivere.dev/mcp).
Is the Vivere MCP server safe to use?
Vivere scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Vivere MCP server expose?
Vivere exposes 7 tools: list_pages, list_monitors, get_monitor, create_monitor, check_in, and 2 more. Their descriptions and schemas cost roughly 648 tokens of context every time the server is loaded.
Does the Vivere MCP server require authentication?
Yes. Vivere asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Vivere MCP server still maintained?
Vivere is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.