# Relvato [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/Relvato/relvato-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/relvato

## Description
Website monitoring: add sites, configure and run monitors, read health, review results, apply fixes.

## Tools
Capabilities this server exposes over MCP:

- **list_sites** — List the account's websites and whether each is ready to run monitors.
- **add_site** — Add a website and get its setup step: connect the WordPress plugin, or verify the domain.
- **verify_site** — Check that setup step: the plugin connection, or the domain-verification DNS record or meta tag.
- **start_monitoring_for_goals** — Pick what matters (checkout, security, search, speed, …) and get the monitors that cover it on your plan.
- **list_checks** — The monitors you can add to a site: what each catches, whether your plan includes it, and which are recommended.
- **add_checks** — Add monitors to a site; each one reports added, already there, or why not.
- **dismiss_recommendation** — Stop recommending a monitor for a site, or bring dismissed recommendations back.
- **calibrate_site** — WooCommerce: read the store again (a product to buy, checkout type, currency) after it changed.
- **verify_vitals_beacon** — Check the real-user Web Vitals beacon is installed.
- **site_overview** — Plain-language health verdict: what needs attention, every monitor with its latest run and schedule, plan usage and, on WordPress, the site's AI abilities.
- **get_site_health** — Pass rate now and over 30 days, the trend over 28–182 days, each group's briefing, and probe uptime with incidents.
- **get_performance** — Lab and real-user Core Web Vitals, what slows the site down, and the top fixes with steps.
- **get_check** — One monitor in full: schedule, its own settings (pages, masks, checkout details, …), ignored findings, its recipe if AI-written, latest run.
- **list_runs** — Recent runs, newest first — by site, monitor or status, with paging.
- **get_run** — One run in detail: steps, findings, visual comparisons with image links, the fix it proposes, plugins it can update.
- **get_fix_prompt** — For a run that found a problem: the same brief Relvato's own AI answers, to reason about the likely cause and fixes.
- **get_updates** — WordPress: auto-update windows and what they updated or rolled back, held versions, safe updates, hardening.
- **get_safe_update** — Follow a safe plugin update or deactivation until it passes or is undone.
- **get_quarantine** — Quarantine mode: available or not, on until when, every change it saw, past sessions.
- **get_activity_log** — WordPress: sign-ins, failed sign-ins, accounts, updates, settings and file edits, within your plan's history.
- **get_notifications** — The dashboard's notifications: failing monitors, plugin or beacon problems, paused channels, billing.
- **get_site_settings** — A site's settings — what an agent may change and what stays in the dashboard (never secret values).
- **get_alert_settings** — Who is told about what: frequency, severity, each channel's state and routing — no URLs or secrets.
- **get_status_pages** — Status pages and client reports: settings only, never a private link or recipients' addresses.
- **list_heartbeats** — A site's heartbeats (cron jobs that check in): state, schedule, last ping, missed check-ins — and the ping URLs on full access.
- **update_check** — Turn a monitor on or off, or change when it runs: schedule, re-runs on WordPress updates, random extra runs.
- **pause_monitor_group** — Pause a whole monitoring group for 1 hour, 24 hours or until resumed, during maintenance; exactly the monitors it switched off come back on.
- **resume_monitor_group** — Resume a paused group now; a monitor the plan no longer allows stays off, with the reason.
- **update_visual_monitor** — Add pages of your own by address to the visual monitor, set masks, devices, browsers and the threshold.
- **update_check_settings** — A monitor's own settings: checkout details, extra pages to scan, what the site's AI feature must answer, DKIM selectors, …
- **add_custom_check** — Describe what must be true on a page; Relvato's AI writes the monitor.
- **edit_custom_check** — Give a custom monitor a new goal or page; the AI writes a new recipe to approve.
- **reauthor_custom_check** — Answer the AI's question, or have it write a custom monitor's recipe again.
- **approve_custom_check** — Approve a proposed recipe so the custom monitor runs (interactive recipes need an explicit OK).
- **update_site_settings** — Pacing, spacing between runs, firewall retry, flaky-monitor recovery, plugin rollback.
- **update_alert_settings** — Alert timing and minimum severity. Who receives alerts and muting stay in the dashboard.
- **add_heartbeat** — Create a heartbeat for a cron job or backup and get the URL the job requests when it succeeds.
- **update_heartbeat** — Rename, reschedule, pause or resume a heartbeat. Deleting stays in the dashboard.
- **trigger_scan** — Run a site's monitors now — all, one group, or one monitor — and get the run ids back (uses the monthly quota).
- **cancel_queued_runs** — Stop a site's queued runs; the one already going finishes.
- **request_ai_fix** — Ask Relvato's AI for a fix suggestion for a failed run (paid plans).
- **apply_fix** — WordPress: apply the one-click fix a run proposes — only that fix — then re-run the monitor.
- **start_safe_update** — WordPress: update or deactivate a vulnerable plugin, re-check, and undo it if anything breaks.
- **start_quarantine** — After a hack: hourly security runs for 48 hours with plugin updates paused.
- **extend_quarantine** — Keep quarantine mode on for another 48 hours.
- **send_test_alert** — Send a test alert by email, Slack or webhook.
- **resume_webhook** — Turn webhook alerts back on after Relvato paused them for failed deliveries.
- **report_false_positive** — Tell Relvato's team a result is wrong; it changes nothing on the run.
- **ignore_finding** — Stop a finding from counting on a monitor (undoable). Only when you confirm it's expected.
- **unignore_finding** — Make an ignored finding count again.
- **accept_visual_change** — Make this run's screenshot the new baseline for a page (undoable).
- **ignore_visual_change** — Ignore the area that changed on a page from now on (undoable).
- **flag_visual_change_as_problem** — Mark a visual change the AI let pass as a failure.
- **undo_visual_review** — Undo the last visual accept or ignore.
- **accept_structure_change** — Adopt a page's new structure as its baseline (undoable).
- **ignore_structure_change** — Ignore specific element changes on a page (undoable).
- **undo_structure_review** — Undo the last structure accept or ignore.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "relvato": {
    "url": "https://app.relvato.com/api/mcp"
  }
}
```

## Documentation

## What Relvato MCP server does

Relvato MCP server exposes Relvato's hosted monitoring service to MCP-compatible clients. Relvato runs checks in a real browser against websites, including sign-ups, logins, checkout, payments, page speed, search visibility, and security. The service works with any website, while WordPress and WooCommerce sites support deeper setup and maintenance workflows.

Agents can create or verify sites, choose monitoring goals, add checks, and adjust schedules. They can also read current and historical health, performance data, monitor configuration, run details, visual comparisons, notifications, status-page settings, and heartbeat activity. Some tools can change monitoring or follow proposed WordPress updates, so access level matters.

## How it works

The repository does not contain the monitoring service itself. It provides connection details, the MCP registry entry, and client-specific assets such as the Claude Code plugin and Gemini CLI extension. The hosted endpoint is `https://app.relvato.com/api/mcp`, using stateless JSON-RPC over streamable HTTP.

Authentication is handled either through Relvato sign-in or an API key. Sign-in uses OAuth 2.1 and is available in clients that support Client ID Metadata Documents. API keys use an `Authorization: Bearer rlv_...` header or the equivalent `x-api-key` header. Read-only keys expose read tools; full-access keys can also add and configure sites and monitors, run scans, and apply fixes proposed by runs.

## Setup and configuration

Add the hosted HTTP endpoint to the MCP client rather than installing a local server. Claude, VS Code, and Claude Code can use the sign-in flow described in the project documentation. Cursor, Gemini CLI, Cline, and DeepSeek Harness use an API key; Gemini CLI also provides an extension, and Claude Code provides an optional plugin with setup, post-deploy checking, and failure-fixing skills.

After connecting, the agent can add a website. The setup step depends on the site: WordPress sites require the Relvato plugin connection, while other sites require domain verification through a DNS record or meta tag. WooCommerce sites can be recalibrated when product, checkout, or currency details change. API keys are shown once and should not be committed to project files.

## Tools and capabilities

The exposed tools cover several operational areas:

- Site onboarding, verification, monitoring goals, check selection, recommendations, and WooCommerce calibration.
- Health summaries, pass rates, trends, uptime incidents, Core Web Vitals, monitor details, runs, findings, image comparisons, and fix briefs.
- Monitor schedules, visual-monitor pages and masks, check-specific settings, group pauses, resumptions, and post-update reruns.
- WordPress update windows, safe updates, quarantine sessions, activity logs, notifications, site settings, alert routing, status-page settings, and heartbeats.

The `get_fix_prompt` tool supplies a run's troubleshooting brief, while `get_run` reports findings, proposed fixes, visual comparisons, and plugins that may be updated. Tools that modify sites or monitoring require full access or an authorized sign-in with write permissions.

## Limitations and notes

Relvato MCP server is hosted, so the repository is not a self-hosted monitoring implementation. A client must support remote streamable HTTP and either Relvato's sign-in method or API-key headers. Clients without Client ID Metadata Document support cannot use the sign-in flow and need an API key.

Read-only credentials cannot make changes. Some information is intentionally withheld by tools: site settings do not expose secret values, alert settings omit URLs and secrets, and status-page settings do not return private links or recipient addresses. Monitoring runs consume the account's monthly quota, and plan limits determine which checks can be added or resumed.

_Full upstream README: https://allmcps.com/mcp/relvato/readme_