Vivere

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

Sollte ich dies verwenden

Qualität und Sicherheit

A
Qualität der Beschreibung
94%
Vollständigkeit des Schemas
87%
Qualität der Benennung
100%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~1,049Tokens (Tool-Definitionen)
~876 BTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (0.82% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

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

Remote-Endpunkte

https://vivere.dev/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (7)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢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.

Eingabe-Schema

{
  "type": "object",
  "properties": {}
}
🟢list_monitors(page_id)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "page_id": {
      "description": "Only this page (from list_pages)",
      "type": "integer"
    }
  }
}
🟢get_monitor(id, page_id, slug)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "id": {
      "description": "Monitor id, for monitors this account owns or edits",
      "type": "string"
    },
    "page_id": {
      "description": "Page id, with slug",
      "type": "integer"
    },
    "slug": {
      "description": "Monitor slug, with page_id",
      "type": "string"
    }
  }
}
🟡create_monitor(cron, grace, interval, kind, name, ...)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "cron": {
      "description": "Heartbeat alternative to period: five-field cron expression, e.g. '0 2 * * *'.",
      "type": "string"
    },
    "grace": {
      "description": "Heartbeat: how late a check-in may be before alerting, e.g. 15m. Default 15m.",
      "type": "string"
    },
    "interval": {
      "description": "HTTP check: how often to request it, e.g. 5m.",
      "type": "string"
    },
    "kind": {
      "description": "heartbeat (the job pings us) or http (we request a URL)",
      "enum": [
        "heartbeat",
        "http"
      ],
      "type": "string"
    },
    "name": {
      "description": "Human name, e.g. 'nightly report agent'",
      "type": "string"
    },
    "page_id": {
      "description": "Page to put it on (from list_pages). Default: the account's first page.",
      "type": "integer"
    },
    "period": {
      "description": "Heartbeat: expected time between successful check-ins, e.g. 30m, 1h, 1d. Default 1h.",
      "type": "string"
    },
    "tags": {
      "description": "Optional space-separated tags.",
      "type": "string"
    },
    "timezone": {
      "description": "IANA timezone for the cron expression, e.g. Asia/Seoul. Default UTC.",
      "type": "string"
    },
    "url": {
      "description": "HTTP check: the public URL to request.",
      "type": "string"
    }
  },
  "required": [
    "name"
  ]
}
🟢check_in(message, monitor_id, status)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "message": {
      "description": "Optional summary or error text to store with the run",
      "type": "string"
    },
    "monitor_id": {
      "description": "Monitor id (the last path segment of the ping URL)",
      "type": "string"
    },
    "status": {
      "description": "Default success",
      "enum": [
        "success",
        "start",
        "fail"
      ],
      "type": "string"
    }
  },
  "required": [
    "monitor_id"
  ]
}
⚪pause_monitor(id)

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

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "id": {
      "description": "Monitor id",
      "type": "string"
    }
  },
  "required": [
    "id"
  ]
}
⚪resume_monitor(id)

Resume a paused monitor.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "id": {
      "description": "Monitor id",
      "type": "string"
    }
  },
  "required": [
    "id"
  ]
}

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet7 Tools
verifiziertVersion nicht aufgezeichnet7 Tools