Vivere MCP MCP server

An official MCP server by Vivere that allows AI agents to manage uptime monitoring for cron jobs and automations. Agents can create monitors, pause or resume them, and report check-in statuses (success, start, fail) to trigger alerts when scheduled tasks stop running.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Vivere

MCP endpoint (Streamable HTTP)

https://vivere.dev/mcp

Vendor documentation

What you can do with it

Create heartbeat monitors for scheduled tasks
Report check-in status for running jobs
Pause or resume active monitors
List monitors and pages with access

Tools advertised by the last live check:

list_pages
list_monitors
get_monitor
create_monitor
check_in
pause_monitor
resume_monitor

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add vivere-mcp --url https://vivere.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable vivere-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "vivere-mcp": {
      "type": "streamableHttp",
      "url": "https://vivere.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start vivere-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "vivere-mcp": {
      "type": "http",
      "url": "https://vivere.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http vivere-mcp https://vivere.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "vivere-mcp": {
      "serverUrl": "https://vivere.dev/mcp"
    }
  }
}

See all 957

Do you run Vivere MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing