Relvato

Official57 tools

by Relvato

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

Model Context Protocol (MCP) Server: com.relvato/relvato

The com.relvato/relvato MCP server provides functionality for website monitoring. It supports workflows to list sites and checks, run scans, read results, and fix prompts. The server description indicates it is oriented around monitoring site status and acting on scan outputs.

🛠️ Key Features

List sites
List checks
Run scans
Read results
Fix prompts

🚀 Use Cases

Monitor a set of websites for scheduled or on-demand scans
Review scan outputs and results for tracked sites and checks
Apply corrective prompt updates based on monitoring outcomes

⚡ Developer Benefits

Centralized access to site/check listing and scan execution
Programmatic retrieval of monitoring results

⚠️ Limitations

Capabilities are limited to what is described: website monitoring, scan execution, result reading, and prompt fixing.

Topics

gemini-cli-extensionmcpmcp-servermodel-context-protocol

Captured live from the server via tools/list.

list_sites

List the websites in this Relvato account, with whether each is ready to run monitors.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

add_site

Start monitoring a website. Returns the site and the setup step the owner must complete before any monitor runs: connect the WordPress plugin, or verify the domain (the only option for non-WordPress sites). If the account already has a site on the same domain, that site is returned instead of a duplicate. How ownership is proven: https://www.relvato.com/docs/verify-site-ownership

Parameters3

url	string	required	The site's address, e.g. https://example.com
name	string	optional	Display name (defaults to the domain)
platform	string	required	"wordpress" for WordPress/WooCommerce (deepest monitors via the Relvato plugin); "other" for any other site or AI-built app (public-page monitors, domain verification).

Raw schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The site's address, e.g. https://example.com"
    },
    "name": {
      "type": "string",
      "description": "Display name (defaults to the domain)"
    },
    "platform": {
      "type": "string",
      "enum": [
        "wordpress",
        "other"
      ],
      "description": "\"wordpress\" for WordPress/WooCommerce (deepest monitors via the Relvato plugin); \"other\" for any other site or AI-built app (public-page monitors, domain verification)."
    }
  },
  "required": [
    "url",
    "platform"
  ],
  "additionalProperties": false
}

verify_site

Check whether the site's ownership is proven: probes the WordPress plugin connection and/or looks for the domain-verification DNS TXT record / meta tag, or (method gsc / bing) asks Google Search Console / Bing Webmaster Tools. Returns the updated setup state. Docs: https://www.relvato.com/docs/verify-site-ownership

Parameters2

siteId	string	required	The site id
method	string	optional	Domain verification only: check just this method (default: DNS and meta tag). gsc / bing ask Google Search Console / Bing Webmaster Tools whether the account connected to the site (in the dashboard) owns it — Search Console owners only, not full or restricted users

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    },
    "method": {
      "type": "string",
      "enum": [
        "dns",
        "meta",
        "gsc",
        "bing"
      ],
      "description": "Domain verification only: check just this method (default: DNS and meta tag). gsc / bing ask Google Search Console / Bing Webmaster Tools whether the account connected to the site (in the dashboard) owns it — Search Console owners only, not full or restricted users"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

start_monitoring_for_goals

The onboarding shortcut: pick what matters and Relvato adds the monitors that cover it on the current plan (plus uptime, SSL, errors, maintenance mode and structure). Goals: flows (checkout and sign-in), security, search, design, compliance (law compliance — accessibility today), speed, domain, custom, ai.

Parameters2

siteId	string	required	The site id
goals	array	required

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    },
    "goals": {
      "type": "array",
      "minItems": 1,
      "items": {
        "type": "string",
        "enum": [
          "flows",
          "security",
          "search",
          "design",
          "compliance",
          "speed",
          "domain",
          "custom",
          "ai"
        ]
      }
    }
  },
  "required": [
    "siteId",
    "goals"
  ],
  "additionalProperties": false
}

list_checks

The monitors that can be added to a site: key, what it catches, whether the current plan allows it, whether it's recommended for this site, and whether it's already added.

Parameters1

siteId

string

required

The site id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

add_checks

Add monitors to a site by key (from list_checks). Each key reports added / exists / rejected with the reason (plan, active-monitor limit, needs the WordPress plugin). New monitors get a daily schedule on plans that run daily (Pro and up) and a weekly one on Free, plus a re-run when the site changes on Pro and up (WordPress plugin updates, or pushes via the GitHub App).

Parameters2

siteId	string	required	The site id
keys	array	required	Check keys, e.g. ["uptime", "ssl", "error-scan"]

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    },
    "keys": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "maxItems": 30,
      "description": "Check keys, e.g. [\"uptime\", \"ssl\", \"error-scan\"]"
    }
  },
  "required": [
    "siteId",
    "keys"
  ],
  "additionalProperties": false
}

dismiss_recommendation

Stop recommending a monitor for a site (list_checks marks recommendations), or bring every dismissed recommendation back with restoreAll.

Parameters3

siteId	string	required	The site id
key	string	optional	The monitor key to stop recommending
restoreAll	boolean	optional

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    },
    "key": {
      "type": "string",
      "description": "The monitor key to stop recommending"
    },
    "restoreAll": {
      "type": "boolean"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

calibrate_site

WordPress / WooCommerce: have Relvato read the store again (a product to buy, checkout type, guest checkout, currency) after the store changed. Runs in the background.

Parameters1

siteId

string

required

The site id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

verify_vitals_beacon

Check that the real-user Web Vitals beacon is on the site (its homepage, or data already arriving). get_site_settings has the snippet to install.

Parameters1

siteId

string

required

The site id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

site_overview

Plain-language health verdict for a site: what needs attention (real issues vs likely false positives), each monitor with its latest run and schedule, setup state, recommended monitors not yet added, and the account's run usage. On WordPress 6.9+ it also lists the site's AI abilities (WordPress Abilities API) from the latest exposure scan: which plugin registered each, whether AI assistants (MCP Adapter) or REST clients can use it, which ones anyone can run without signing in, and which can delete data.

Parameters1

siteId

string

required

The site id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

get_site_health

How a site has been doing: the share of monitors passing now (the Overview's "Monitors passing") and each of the last 30 days, the trend over 28, 90 or 182 days, each monitoring group's briefing (what needs attention, its likely cause and fix), and — on paid plans — uptime from Relvato's own probes (availability % and incidents over 30 days).

Parameters2

siteId	string	required	The site id
range	number	optional	Trend length in days (default 28)

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    },
    "range": {
      "type": "number",
      "enum": [
        28,
        90,
        182
      ],
      "description": "Trend length in days (default 28)"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

get_performance

A site's speed: the performance summary, lab Core Web Vitals, real visitors' LCP / INP / CLS (p75, last 7 days against the 28 before, per page type and device), what slows it (the elements, images and scripts behind slow visits) and the top fixes with steps.

Parameters1

siteId

string

required

The site id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

get_check

One monitor in full: on/off, when it runs (schedule, time zone, re-runs on WordPress updates, random extra runs, and whether the plan allows them), its own settings (the visual monitor's pages with their keys, masks, devices, browsers and threshold; the checkout's product, coupon, shipping and field answers; extra pages to scan; …), which settings sections update_check_settings accepts for it, the findings the user ignored, an AI-authored monitor's goal, status, question and recipe steps, and its latest run.

Parameters1

checkId

string

required

The monitor's id (from site_overview or add_checks)

Raw schema

{
  "type": "object",
  "properties": {
    "checkId": {
      "type": "string",
      "description": "The monitor's id (from site_overview or add_checks)"
    }
  },
  "required": [
    "checkId"
  ],
  "additionalProperties": false
}

list_runs

Recent runs, newest first, optionally for one site, one monitor or one status. Each has the monitor (checkId, checkName, and its key in `journey`), status, trigger, timing and its error / warning; get_run has the detail. For older runs pass `before` (the startedAt of the last run you got).

Parameters5

siteId	string	optional	Only runs for this site id
checkId	string	optional	Only runs of this monitor
status	string	optional	Only runs with this status (a failure the user resolved counts as passed)
before	string	optional	Only runs started before this time (ISO 8601): the next page
limit	number	optional	Max runs, 1-100 (default 25)

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "Only runs for this site id"
    },
    "checkId": {
      "type": "string",
      "description": "Only runs of this monitor"
    },
    "status": {
      "type": "string",
      "enum": [
        "passed",
        "failed",
        "skipped",
        "running",
        "queued"
      ],
      "description": "Only runs with this status (a failure the user resolved counts as passed)"
    },
    "before": {
      "type": "string",
      "description": "Only runs started before this time (ISO 8601): the next page"
    },
    "limit": {
      "type": "number",
      "description": "Max runs, 1-100 (default 25)"
    }
  },
  "additionalProperties": false
}

get_run

One run in detail: status, error and warnings (each with its key for ignore_finding; ignored ones marked; one Relvato never fixes carries noFix — why, and what to do instead), each step, visual comparisons (each with its comparisonId, links to the screenshot, the baseline and the diff that work for 10 minutes, and whether a decision on it can be undone), metrics, the one-click fix the run proposes if any, and Relvato AI's suggestion once requested. Large metrics are compacted, never the findings: daily series become summaries and what was left out is listed in metricsTrimmed.

Parameters1

runId

string

required

The run id

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "The run id"
    }
  },
  "required": [
    "runId"
  ],
  "additionalProperties": false
}

get_fix_prompt

For a run that failed or found a problem: the same brief Relvato's own AI answers when the user clicks "Suggest a fix" — the site's detected stack, what the monitor verifies, what changed on the site just before, the exact error and findings, whether it was already failing earlier, and for Google / Bing Search the evidence that rules causes out. Use it as context to explain the likely cause and fixes; applying a fix stays with the user.

Parameters1

runId

string

required

The run id

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "The run id"
    }
  },
  "required": [
    "runId"
  ],
  "additionalProperties": false
}

get_updates

WordPress sites: the safe auto-update policy and its recent windows (what was updated, rolled back or skipped, and why), plugin versions held back after a rollback, safe updates or deactivations Relvato made and their outcome, and the hardening settings that are on.

Parameters1

siteId

string

required

The site id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

get_safe_update

Follow a safe update or deactivation: applying → verifying → passed, or reverted with the monitors that broke.

Parameters1

changeId

string

required

From start_safe_update

Raw schema

{
  "type": "object",
  "properties": {
    "changeId": {
      "type": "string",
      "description": "From start_safe_update"
    }
  },
  "required": [
    "changeId"
  ],
  "additionalProperties": false
}

get_quarantine

Quarantine mode (WordPress, paid plans): 48 hours of hourly security runs after a cleanup, with plugin updates paused. Whether it's available, on, until when, every change it saw (expected or not), which monitors it watches, the runs it would use, and past sessions.

Parameters1

siteId

string

required

The site id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

get_activity_log

WordPress sites: who did what — sign-ins and failed sign-ins (with the network, not the full address), accounts and roles, application passwords, plugin / theme / core updates, setting and file edits, PHP errors and failed emails — newest first, within the plan's history (7 to 365 days).

Parameters5

siteId	string	required	The site id
filter	string	optional
search	string	optional	Only events mentioning this (a username, a plugin)
days	number	optional	How far back (up to the plan's history)
limit	number	optional	Max events, 1-300 (default 100)

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    },
    "filter": {
      "type": "string",
      "enum": [
        "all",
        "logins",
        "people",
        "changes",
        "errors"
      ]
    },
    "search": {
      "type": "string",
      "description": "Only events mentioning this (a username, a plugin)"
    },
    "days": {
      "type": "number",
      "description": "How far back (up to the plan's history)"
    },
    "limit": {
      "type": "number",
      "description": "Max events, 1-300 (default 100)"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

get_notifications

The dashboard's notifications: failing monitors, a disconnected or outdated WordPress plugin, a silent real-user beacon, domain and ownership problems, safe updates that need a look, paused Slack or webhook alerts, and billing.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

get_site_settings

A site's Settings tab as values: what update_site_settings may change (name, request pacing, spacing between runs, firewall retry delay, flaky-monitor recovery streak, plugin rollback, counting Relvato's own visits in real-user data), what only the dashboard changes (browser identity, proxy, firewall allowlist token — never its value — GitHub, Google / Bing connections), the WordPress plugin's version, and the real-user beacon snippet.

Parameters1

siteId

string

required

The site id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

get_alert_settings

Who is told about what: how often (instant, daily / weekly digest), the minimum severity, each channel (email, Slack, webhook — whether the plan includes it, whether it's set up, paused, and `on` = alerts actually go out on it), which sites are muted and which monitor types go to which channel (only channels that are on). Never includes webhook URLs or secrets. Changing them is done by the user in Alert settings.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

get_status_pages

Public status pages (title, public link, sites, on/off) and monthly client reports per site (on/off, how many recipients, last sent), plus the report branding. Never a report's private link or recipients' addresses. Edited in the dashboard's Agency page.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

list_heartbeats

A site's heartbeats — cron jobs, backups and scheduled tasks that check in by requesting their own URL: each one's state (new = waiting for its first ping, up, down), schedule (period + grace, in seconds), last ping, when the next is due at the latest, whether the plan covers it, recent missed or failed check-ins and pings, plus the account's heartbeats used / allowed. Full-access connections also get each ping URL (it's what the job requests; anyone with it can send pings).

Parameters1

siteId

string

required

The site's id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site's id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

update_check

Turn a monitor on or off, or change when it runs: its schedule (up to weekly on Free, daily on Pro, hourly on Business, every 15 minutes on Agency), re-runs when the WordPress site changes (plugin, theme, core or WooCommerce updates; Pro and up) and random extra runs (Business and up). Only the fields you pass change. Its own settings (pages, URLs, checkout details) are changed with update_check_settings or update_visual_monitor.

Parameters8

checkId	string	required	The monitor's id (from site_overview or add_checks)
enabled	boolean	optional	Turn the monitor on or off
schedule	string	optional	Recurring schedule
at	string	optional	Daily/weekly run time, HH:MM (24h)
tz	string	optional	IANA timezone for `at`, e.g. Europe/Berlin
dow	number	optional	Weekly only: weekday, 0 = Sunday … 6 = Saturday
events	array	optional	WordPress sites only: re-run when these change. [] = none. A monitor's built-in triggers (e.g. the admin roster's role changes) are kept.
random	object \| null	optional	Random extra runs (times per days), with an off or weekly schedule; null turns them off

Raw schema

{
  "type": "object",
  "properties": {
    "checkId": {
      "type": "string",
      "description": "The monitor's id (from site_overview or add_checks)"
    },
    "enabled": {
      "type": "boolean",
      "description": "Turn the monitor on or off"
    },
    "schedule": {
      "type": "string",
      "enum": [
        "off",
        "weekly",
        "daily",
        "6h",
        "hourly",
        "fastest"
      ],
      "description": "Recurring schedule"
    },
    "at": {
      "type": "string",
      "description": "Daily/weekly run time, HH:MM (24h)"
    },
    "tz": {
      "type": "string",
      "description": "IANA timezone for `at`, e.g. Europe/Berlin"
    },
    "dow": {
      "type": "number",
      "description": "Weekly only: weekday, 0 = Sunday … 6 = Saturday"
    },
    "events": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "plugin",
          "theme",
          "core",
          "woocommerce"
        ]
      },
      "description": "WordPress sites only: re-run when these change. [] = none. A monitor's built-in triggers (e.g. the admin roster's role changes) are kept."
    },
    "random": {
      "type": [
        "object",
        "null"
      ],
      "properties": {
        "times": {
          "type": "number",
          "description": "1-100 runs"
        },
        "days": {
          "type": "number",
          "description": "over 1-365 days"
        }
      },
      "required": [
        "times",
        "days"
      ],
      "additionalProperties": false,
      "description": "Random extra runs (times per days), with an off or weekly schedule; null turns them off"
    }
  },
  "required": [
    "checkId"
  ],
  "additionalProperties": false
}

pause_monitor_group

Pause one monitoring group on a site for 1 hour, 24 hours or until resumed (maintenance, a redesign, a migration). The group's monitors that are on are switched off and remembered; when the time is up, or with resume_monitor_group, exactly those are switched back on, as far as the plan allows. Pausing a group that's already paused changes when it resumes. Pausing Security while the site is in quarantine stays in the dashboard. Tell the user which monitors stop watching and for how long, and get their go-ahead first. site_overview lists paused groups.

Parameters3

siteId	string	required	The site id
group	string	required	The monitoring group: uptime = uptime, heartbeats and port monitors; flow = user flows; security; design; performance; seo; domain; compliance = legal compliance (accessibility)
duration	string	required	How long: 1 hour, 24 hours, or until resumed

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    },
    "group": {
      "type": "string",
      "enum": [
        "flow",
        "security",
        "design",
        "performance",
        "seo",
        "domain",
        "compliance",
        "uptime"
      ],
      "description": "The monitoring group: uptime = uptime, heartbeats and port monitors; flow = user flows; security; design; performance; seo; domain; compliance = legal compliance (accessibility)"
    },
    "duration": {
      "type": "string",
      "enum": [
        "1h",
        "24h",
        "until"
      ],
      "description": "How long: 1 hour, 24 hours, or until resumed"
    }
  },
  "required": [
    "siteId",
    "group",
    "duration"
  ],
  "additionalProperties": false
}

resume_monitor_group

Resume a paused monitoring group now: the monitors its pause switched off go back on (a monitor the plan no longer allows stays off, with the reason in keptOff). A group that isn't paused is left as it is.

Parameters2

siteId	string	required	The site id
group	string	required	The paused group (site_overview pausedGroups)

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    },
    "group": {
      "type": "string",
      "enum": [
        "flow",
        "security",
        "design",
        "performance",
        "seo",
        "domain",
        "compliance",
        "uptime"
      ],
      "description": "The paused group (site_overview pausedGroups)"
    }
  },
  "required": [
    "siteId",
    "group"
  ],
  "additionalProperties": false
}

update_visual_monitor

Edit the visual regression monitor: add pages (a built-in one by key, or a page of your own by its address on the site, e.g. "/pricing"; up to 10 of your own), rename or re-point a page of your own, change any page's masks (CSS selectors painted over before comparing, for clocks, carousels, ads), remove pages, and set devices, browsers, full-page capture, the change threshold (percent) and the AI review. A page whose masks or address change gets a new baseline: its next run captures one for the user to approve. At most 40 screenshots a run (pages × devices × browsers). get_check lists the current pages and their keys.

Parameters9

checkId	string	required	The visual regression monitor's id
add	array	optional
update	array	optional
remove	array	optional	Keys of pages to stop checking
devices	array	optional
browsers	array	optional
fullPage	boolean	optional	Capture the whole page (default) or only the first screen
thresholdPercent	number	optional	How much of a page may change before it counts, 0-50 (default ~1)
aiReview	boolean	optional	Let AI review a change before it alerts (default on)

Raw schema

{
  "type": "object",
  "properties": {
    "checkId": {
      "type": "string",
      "description": "The visual regression monitor's id"
    },
    "add": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "page": {
            "type": "string",
            "enum": [
              "home",
              "shop",
              "product",
              "category",
              "checkout"
            ],
            "description": "A built-in page Relvato finds by itself"
          },
          "url": {
            "type": "string",
            "description": "Or a page of your own: its address on the site (full URL or a path like /pricing)"
          },
          "label": {
            "type": "string",
            "description": "A name for a page of your own (up to 60 characters)"
          },
          "masks": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "CSS selectors to mask on this page"
          }
        },
        "additionalProperties": false
      }
    },
    "update": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "key": {
            "type": "string",
            "description": "The page's key (from get_check)"
          },
          "url": {
            "type": "string",
            "description": "Pages of your own: a new address"
          },
          "label": {
            "type": "string",
            "description": "Pages of your own: a new name"
          },
          "masks": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Replaces the page's masks ([] removes them)"
          }
        },
        "required": [
          "key"
        ],
        "additionalProperties": false
      }
    },
    "remove": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Keys of pages to stop checking"
    },
    "devices": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "desktop",
          "mobile"
        ]
      }
    },
    "browsers": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "chromium",
          "firefox",
          "webkit"
        ]
      }
    },
    "fullPage": {
      "type": "boolean",
      "description": "Capture the whole page (default) or only the first screen"
    },
    "thresholdPercent": {
      "type": "number",
      "description": "How much of a page may change before it counts, 0-50 (default ~1)"
    },
    "aiReview": {
      "type": "boolean",
      "description": "Let AI review a change before it alerts (default on)"
    }
  },
  "required": [
    "checkId"
  ],
  "additionalProperties": false
}

update_check_settings

Change a monitor's own settings. Each monitor takes only its sections (get_check lists them as editable.sections): checkout (checkout monitors), devices (flow and page monitors), errorScan, brokenLinks, accessibilityPages (accessibility), uptime (the URL, text that must / must not appear, accepted statuses, timeout, alert after N minutes, maintenance windows, an API endpoint's method / body / JSON rules), aiOutput, browseUrl (storefront), shopUrl / productUrl (prices), dkimSelectors (email authentication), structurePages (structure drift), webVitalsDevices (Core Web Vitals). Every address must be a full URL on the site's own domain. A section you pass replaces that section; the rest stays. Turning it on or off and its schedule: update_check. The visual monitor: update_visual_monitor.

Parameters14

checkId	string	required	The monitor's id
checkout	object	optional	Checkout monitors
devices	array	optional	Flow and page monitors
errorScan	object	optional	Extra pages to scan (full URLs on the site) and error texts to ignore
brokenLinks	object	optional	Extra pages to crawl, address fragments to skip, and whether external links are checked too
uptime	object	optional	Uptime: what the probes check and when they alert. The whole section is replaced: fields left out go back to their defaults (except maintenance, kept unless sent)
accessibilityPages	array	optional	Accessibility: extra pages to test on top of the key pages (full URLs on the site, up to 20). A new page's issues are reviewed on its first scan, not failed
aiOutput	object	optional	The site's own AI feature: its endpoint (full URL on the site), a fixed prompt, and what the answer must (not) contain
browseUrl	string	optional	Storefront: the shop page (blank = the calibrated one)
shopUrl	string	optional	Prices: the shop page
productUrl	string	optional	Prices: a sample product
dkimSelectors	array	optional	Email authentication: your mail provider's DKIM selectors (up to 10)
structurePages	array	optional	Structure drift: pages to fingerprint
webVitalsDevices	array	optional	Core Web Vitals: devices to measure

Raw schema

{
  "type": "object",
  "properties": {
    "checkId": {
      "type": "string",
      "description": "The monitor's id"
    },
    "checkout": {
      "type": "object",
      "description": "Checkout monitors",
      "properties": {
        "depth": {
          "type": "string",
          "enum": [
            "ready",
            "order"
          ],
          "description": "\"ready\" stops at the payment step; \"order\" places a REAL test order (the WordPress plugin marks it, keeps it out of stock, analytics and ad platforms, and removes it)"
        },
        "productUrl": {
          "type": "string",
          "description": "The product to buy (full URL on the site; blank = Relvato picks one)"
        },
        "verifyEmail": {
          "type": "boolean",
          "description": "Order mode: confirm the order email arrives"
        },
        "paymentMethod": {
          "type": "string",
          "enum": [
            "cod",
            "free"
          ]
        },
        "coupon": {
          "type": [
            "object",
            "null"
          ],
          "properties": {
            "code": {
              "type": "string"
            },
            "expect": {
              "type": "string",
              "enum": [
                "applies",
                "rejected"
              ]
            }
          },
          "required": [
            "code"
          ],
          "additionalProperties": false
        },
        "shipping": {
          "type": [
            "object",
            "null"
          ],
          "properties": {
            "method": {
              "type": "string"
            },
            "require": {
              "type": "boolean"
            }
          },
          "additionalProperties": false
        },
        "fieldAnswers": {
          "type": "array",
          "maxItems": 12,
          "items": {
            "type": "object",
            "properties": {
              "match": {
                "type": "string"
              },
              "value": {
                "type": "string"
              }
            },
            "required": [
              "match",
              "value"
            ],
            "additionalProperties": false
          },
          "description": "Answers for checkout fields Relvato can't fill by itself: match = the field's label or name, value = what to enter"
        },
        "expect": {
          "type": [
            "object",
            "null"
          ],
          "properties": {
            "shipping": {
              "description": "\"free\", \"charged\" or an amount"
            },
            "tax": {
              "description": "\"applied\", \"none\" or an amount"
            },
            "discount": {
              "description": "\"applied\", \"none\" or an amount"
            },
            "total": {
              "type": "object",
              "properties": {
                "equals": {
                  "type": "number"
                },
                "min": {
                  "type": "number"
                },
                "max": {
                  "type": "number"
                }
              },
              "additionalProperties": false
            }
          },
          "additionalProperties": false,
          "description": "What the order totals must be"
        }
      },
      "additionalProperties": false
    },
    "devices": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "desktop",
          "mobile"
        ]
      },
      "description": "Flow and page monitors"
    },
    "errorScan": {
      "type": "object",
      "properties": {
        "urls": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "ignore": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      },
      "required": [
        "urls",
        "ignore"
      ],
      "additionalProperties": false,
      "description": "Extra pages to scan (full URLs on the site) and error texts to ignore"
    },
    "brokenLinks": {
      "type": "object",
      "properties": {
        "urls": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "ignore": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "checkExternal": {
          "type": "boolean"
        }
      },
      "required": [
        "urls",
        "ignore",
        "checkExternal"
      ],
      "additionalProperties": false,
      "description": "Extra pages to crawl, address fragments to skip, and whether external links are checked too"
    },
    "uptime": {
      "type": "object",
      "properties": {
        "url": {
          "type": "string",
          "description": "Page to check (full URL on the site; blank = the homepage)"
        },
        "expectText": {
          "type": "string",
          "description": "Down if the page doesn't contain this text"
        },
        "absentText": {
          "type": "string",
          "description": "Down if the page contains this text"
        },
        "okStatuses": {
          "type": "string",
          "description": "Accepted status codes, e.g. \"200-299, 301\" (blank = any non-error answer)"
        },
        "timeoutSec": {
          "type": "number",
          "description": "Down if there's no answer within this many seconds (5-30, default 15)"
        },
        "alertAfterMin": {
          "type": "number",
          "description": "Minutes down before alerting (0-60, default 0 = as soon as both regions confirm)"
        },
        "maxResponseMs": {
          "type": "number",
          "description": "The monitor's run warns above this response time (500-30000, default 8000); not counted as down"
        },
        "method": {
          "type": "string",
          "enum": [
            "GET",
            "HEAD",
            "POST"
          ],
          "description": "API endpoints: the request method (default GET)"
        },
        "body": {
          "type": "string",
          "description": "POST only: the request body (sent as JSON when it parses as JSON; up to 2,000 characters). No custom headers or secrets"
        },
        "json": {
          "type": "array",
          "description": "Rules on a JSON answer (up to 10; down when any fails): the value at `path` (\"status\", \"checks.db.ok\", \"items[0].id\") tested with `op` against `value`",
          "items": {
            "type": "object",
            "properties": {
              "path": {
                "type": "string",
                "description": "Dot path into the JSON answer"
              },
              "op": {
                "type": "string",
                "enum": [
                  "equals",
                  "not-equals",
                  "contains",
                  "exists",
                  "missing",
                  "lt",
                  "gt"
                ]
              },
              "value": {
                "type": "string",
                "description": "What to compare with (a number for lt / gt; not needed for exists / missing)"
              }
            },
            "required": [
              "path",
              "op"
            ],
            "additionalProperties": false
          }
        },
        "maintenance": {
          "type": "array",
          "description": "Maintenance windows (up to 10): no uptime alerts and no Uptime run inside them, and an outage that starts inside one counts as downtime only after it ends. Left out = keep the saved windows; [] clears them. A new one-off window can't start in the past",
          "items": {
            "type": "object",
            "properties": {
              "kind": {
                "type": "string",
                "enum": [
                  "once",
                  "weekly"
                ]
              },
              "from": {
                "type": "string",
                "description": "once: start, ISO 8601 with a time zone"
              },
              "to": {
                "type": "string",
                "description": "once: end, ISO 8601 (at most 7 days after the start)"
              },
              "days": {
                "type": "array",
                "items": {
                  "type": "number"
                },
                "description": "weekly: weekdays, 0 = Sunday … 6 = Saturday"
              },
              "start": {
                "type": "string",
                "description": "weekly: local start time, HH:MM"
              },
              "minutes": {
                "type": "number",
                "description": "weekly: length in minutes (5-720)"
              },
              "tz": {
                "type": "string",
                "description": "weekly: IANA time zone, e.g. Europe/Bucharest"
              },
              "note": {
                "type": "string",
                "description": "Optional label, e.g. \"Host migration\""
              }
            },
            "required": [
              "kind"
            ],
            "additionalProperties": false
          }
        }
      },
      "additionalProperties": false,
      "description": "Uptime: what the probes check and when they alert. The whole section is replaced: fields left out go back to their defaults (except maintenance, kept unless sent)"
    },
    "accessibilityPages": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Accessibility: extra pages to test on top of the key pages (full URLs on the site, up to 20). A new page's issues are reviewed on its first scan, not failed"
    },
    "aiOutput": {
      "type": "object",
      "description": "The site's own AI feature: its endpoint (full URL on the site), a fixed prompt, and what the answer must (not) contain",
      "properties": {
        "endpoint": {
          "type": "string"
        },
        "method": {
          "type": "string",
          "enum": [
            "POST",
            "GET"
          ]
        },
        "prompt": {
          "type": "string"
        },
        "bodyTemplate": {
          "type": "string"
        },
        "responsePath": {
          "type": "string"
        },
        "mustInclude": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "mustExclude": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "minLength": {
          "type": "number"
        },
        "maxLatencyMs": {
          "type": "number"
        },
        "golden": {
          "type": "string"
        }
      },
      "required": [
        "endpoint",
        "prompt",
        "mustInclude",
        "mustExclude"
      ],
      "additionalProperties": false
    },
    "browseUrl": {
      "type": "string",
      "description": "Storefront: the shop page (blank = the calibrated one)"
    },
    "shopUrl": {
      "type": "string",
      "description": "Prices: the shop page"
    },
    "productUrl": {
      "type": "string",
      "description": "Prices: a sample product"
    },
    "dkimSelectors": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Email authentication: your mail provider's DKIM selectors (up to 10)"
    },
    "structurePages": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "home",
          "shop",
          "product",
          "category",
          "checkout"
        ]
      },
      "description": "Structure drift: pages to fingerprint"
    },
    "webVitalsDevices": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "desktop",
          "mobile"
        ]
      },
      "description": "Core Web Vitals: devices to measure"
    }
  },
  "required": [
    "checkId"
  ],
  "additionalProperties": false
}

add_custom_check

Describe in plain words what to verify on a page (e.g. "the Pro plan shows a price", "search for 'shoes' returns results") and Relvato's AI writes a monitor for it, in a minute or two. Follow it with get_check: status goes authoring → proposed (show the user its rationale and steps, then approve_custom_check) or needs-input (answer with reauthor_custom_check) or failed (with advice). Read-only by default; interactive: true lets it click and type (search, filters, forms). Plan-gated; counts toward the active-monitor limit.

Parameters6

siteId	string	required	The site id
url	string	required	The page to check: a full URL on the site
goal	string	required	What must be true on that page, in plain words
name	string	optional	A name for the monitor (defaults to the goal)
authenticated	boolean	optional	WordPress sites: run logged in as Relvato's verification user
interactive	boolean	optional	Allow clicking and typing on the live page

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    },
    "url": {
      "type": "string",
      "description": "The page to check: a full URL on the site"
    },
    "goal": {
      "type": "string",
      "description": "What must be true on that page, in plain words"
    },
    "name": {
      "type": "string",
      "description": "A name for the monitor (defaults to the goal)"
    },
    "authenticated": {
      "type": "boolean",
      "description": "WordPress sites: run logged in as Relvato's verification user"
    },
    "interactive": {
      "type": "boolean",
      "description": "Allow clicking and typing on the live page"
    }
  },
  "required": [
    "siteId",
    "url",
    "goal"
  ],
  "additionalProperties": false
}

edit_custom_check

Give a custom monitor a new goal, page, name or mode. Its current recipe is dropped and the AI writes a new one, which needs approving again before the monitor runs.

Parameters6

checkId	string	required	The custom monitor's id
url	string	required	The page to check: a full URL on the site
goal	string	required	What must be true on that page
name	string	optional	A new name
authenticated	boolean	optional
interactive	boolean	optional

Raw schema

{
  "type": "object",
  "properties": {
    "checkId": {
      "type": "string",
      "description": "The custom monitor's id"
    },
    "url": {
      "type": "string",
      "description": "The page to check: a full URL on the site"
    },
    "goal": {
      "type": "string",
      "description": "What must be true on that page"
    },
    "name": {
      "type": "string",
      "description": "A new name"
    },
    "authenticated": {
      "type": "boolean"
    },
    "interactive": {
      "type": "boolean"
    }
  },
  "required": [
    "checkId",
    "url",
    "goal"
  ],
  "additionalProperties": false
}

reauthor_custom_check

Have the AI write a custom monitor's recipe again: answer its question (status needs-input) with `answer`, or retry after it failed or went stale. The monitor stops running until the new recipe is approved.

Parameters2

checkId	string	required	The custom monitor's id
answer	string	optional	Your reply to the AI's question (get_check custom.question)

Raw schema

{
  "type": "object",
  "properties": {
    "checkId": {
      "type": "string",
      "description": "The custom monitor's id"
    },
    "answer": {
      "type": "string",
      "description": "Your reply to the AI's question (get_check custom.question)"
    }
  },
  "required": [
    "checkId"
  ],
  "additionalProperties": false
}

approve_custom_check

Approve a custom monitor's proposed recipe (status proposed) so it runs and alerts from now on. Show the user its rationale and steps first (get_check). A recipe in interactive mode clicks or types on the live site: approve it only after the user agrees, with ack: true.

Parameters2

checkId	string	required	The custom monitor's id
ack	boolean	optional	Required for an interactive recipe: the user agreed it may act on the live site

Raw schema

{
  "type": "object",
  "properties": {
    "checkId": {
      "type": "string",
      "description": "The custom monitor's id"
    },
    "ack": {
      "type": "boolean",
      "description": "Required for an interactive recipe: the user agreed it may act on the live site"
    }
  },
  "required": [
    "checkId"
  ],
  "additionalProperties": false
}

update_site_settings

Change a site's operational settings. Only the fields you pass change. Browser identity, the proxy, the firewall token, GitHub and search-engine connections, and deleting the site stay in the dashboard.

Parameters8

siteId	string	required	The site id
name	string	optional	Display name
pacingMs	number \| null	optional	Pause between a run's requests, 0-60000 ms; null = automatic
jobSpacingMs	number \| null	optional	Pause between this site's runs, 0-900000 ms; null/0 = none
challengeRetryMs	number \| null	optional	Wait before retrying a run a firewall challenged, 0-3600000 ms; null = 10 minutes, 0 = never
recoverStreak	number \| null	optional	Clean runs before a flaky monitor alerts again, 2-10; null = 5
pluginRollback	boolean	optional	WordPress: roll a plugin update back when it breaks a monitor
rumIncludeOwnChecks	boolean	optional	Count Relvato's own visits in real-user Web Vitals

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    },
    "name": {
      "type": "string",
      "description": "Display name"
    },
    "pacingMs": {
      "type": [
        "number",
        "null"
      ],
      "description": "Pause between a run's requests, 0-60000 ms; null = automatic"
    },
    "jobSpacingMs": {
      "type": [
        "number",
        "null"
      ],
      "description": "Pause between this site's runs, 0-900000 ms; null/0 = none"
    },
    "challengeRetryMs": {
      "type": [
        "number",
        "null"
      ],
      "description": "Wait before retrying a run a firewall challenged, 0-3600000 ms; null = 10 minutes, 0 = never"
    },
    "recoverStreak": {
      "type": [
        "number",
        "null"
      ],
      "description": "Clean runs before a flaky monitor alerts again, 2-10; null = 5"
    },
    "pluginRollback": {
      "type": "boolean",
      "description": "WordPress: roll a plugin update back when it breaks a monitor"
    },
    "rumIncludeOwnChecks": {
      "type": "boolean",
      "description": "Count Relvato's own visits in real-user Web Vitals"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

update_alert_settings

Change how often alerts are sent (instant and/or a daily or weekly digest), when the digest goes out, the minimum severity, and whether every run is emailed. Only the fields you pass change. Who gets alerts (the address, Slack, webhooks), muting sites or monitor types, and turning email alerts off stay in the dashboard.

Parameters6

frequency	array	optional
digestTime	string	optional	HH:MM (24h) for the daily / weekly digest
digestWeekday	number	optional	Weekly digest day, 0 = Sunday … 6 = Saturday
timezone	string	optional	IANA time zone for the digest, e.g. Europe/Berlin
minSeverity	string	optional
everyRun	boolean	optional	Email every run, not only problems

Raw schema

{
  "type": "object",
  "properties": {
    "frequency": {
      "type": "array",
      "minItems": 1,
      "items": {
        "type": "string",
        "enum": [
          "instant",
          "daily",
          "weekly"
        ]
      }
    },
    "digestTime": {
      "type": "string",
      "description": "HH:MM (24h) for the daily / weekly digest"
    },
    "digestWeekday": {
      "type": "number",
      "description": "Weekly digest day, 0 = Sunday … 6 = Saturday"
    },
    "timezone": {
      "type": "string",
      "description": "IANA time zone for the digest, e.g. Europe/Berlin"
    },
    "minSeverity": {
      "type": "string",
      "enum": [
        "warning",
        "low",
        "medium",
        "high",
        "critical"
      ]
    },
    "everyRun": {
      "type": "boolean",
      "description": "Email every run, not only problems"
    }
  },
  "additionalProperties": false
}

add_heartbeat

Create a heartbeat for a job the user runs (cron job, backup script, scheduled task, CI job). Returns its ping URL: the job requests it when it succeeds (e.g. `your-job && curl -fsS -m 10 --retry 3 <pingUrl>`), and `<pingUrl>/fail` to report a failure (a POST body is kept with the ping). No ping within period + grace, or a failure, alerts the user at once; a new heartbeat waits for its first ping and never alerts before it. Adds the site's Heartbeats monitor with the first one. Plan limits per account: Free 2, Pro 20, Business 100, Agency 500.

Parameters6

siteId	string	required	The site's id
name	string	required	What the job is, e.g. "Nightly backup"
periodSec	number	optional	How often the job runs, in seconds (60 to 2678400 = 31 days; default 86400 = daily). Ignored when `cron` is set
cron	string	optional	Instead of a period: the job's cron expression (five fields, e.g. "0 3 * * " or "/15 * * * 1-5"; @daily, @hourly … work too). A ping is then due by each time it fires plus the grace
tz	string	optional	The cron expression's IANA time zone, e.g. Europe/Bucharest (default UTC)
graceSec	number	optional	How late a ping may be before it counts as missed, in seconds (60 to 604800 = 7 days; default 3600)

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site's id"
    },
    "name": {
      "type": "string",
      "description": "What the job is, e.g. \"Nightly backup\""
    },
    "periodSec": {
      "type": "number",
      "description": "How often the job runs, in seconds (60 to 2678400 = 31 days; default 86400 = daily). Ignored when `cron` is set"
    },
    "cron": {
      "type": "string",
      "description": "Instead of a period: the job's cron expression (five fields, e.g. \"0 3 * * *\" or \"*/15 * * * 1-5\"; @daily, @hourly … work too). A ping is then due by each time it fires plus the grace"
    },
    "tz": {
      "type": "string",
      "description": "The cron expression's IANA time zone, e.g. Europe/Bucharest (default UTC)"
    },
    "graceSec": {
      "type": "number",
      "description": "How late a ping may be before it counts as missed, in seconds (60 to 604800 = 7 days; default 3600)"
    }
  },
  "required": [
    "siteId",
    "name"
  ],
  "additionalProperties": false
}

update_heartbeat

Rename a heartbeat, change its period or grace, or pause / resume it. Only the fields you pass change. Paused: pings are still recorded but nothing is judged or alerted (an open outage ends without a "back" alert); resumed, it waits for its next ping. Deleting a heartbeat stays in the dashboard.

Parameters7

heartbeatId	string	required	The heartbeat's id (from list_heartbeats or add_heartbeat)
name	string	optional	New name
periodSec	number	optional	How often the job runs, in seconds (60 to 2678400); switches a cron schedule back to a period
cron	string	optional	A cron expression to use instead of the period ("" switches back to the period)
tz	string	optional	The cron expression's IANA time zone
graceSec	number	optional	Grace time in seconds (60 to 604800)
paused	boolean	optional	true pauses it, false resumes it

Raw schema

{
  "type": "object",
  "properties": {
    "heartbeatId": {
      "type": "string",
      "description": "The heartbeat's id (from list_heartbeats or add_heartbeat)"
    },
    "name": {
      "type": "string",
      "description": "New name"
    },
    "periodSec": {
      "type": "number",
      "description": "How often the job runs, in seconds (60 to 2678400); switches a cron schedule back to a period"
    },
    "cron": {
      "type": "string",
      "description": "A cron expression to use instead of the period (\"\" switches back to the period)"
    },
    "tz": {
      "type": "string",
      "description": "The cron expression's IANA time zone"
    },
    "graceSec": {
      "type": "number",
      "description": "Grace time in seconds (60 to 604800)"
    },
    "paused": {
      "type": "boolean",
      "description": "true pauses it, false resumes it"
    }
  },
  "required": [
    "heartbeatId"
  ],
  "additionalProperties": false
}

trigger_scan

Run a site's enabled monitors now — or one group of them (group), or one monitor with checkId, even if it's turned off. Each run counts toward the monthly run quota. Runs go one at a time and take from seconds to a few minutes each, so all of a site's monitors usually take several minutes: the result's estimatedMinutes and tellUser say how long, so tell the user to expect a wait. Returns the runIds to follow with get_run or list_runs; cancel_queued_runs stops the ones that haven't started.

Parameters3

siteId	string	required	The site id
checkId	string	optional	Run only this monitor
group	string	optional	Run only this group's enabled monitors (as the dashboard's Run group): uptime = uptime, heartbeats and port monitors; flow = user flows; security; design; performance; seo; domain; compliance = legal compliance (accessibility)

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    },
    "checkId": {
      "type": "string",
      "description": "Run only this monitor"
    },
    "group": {
      "type": "string",
      "enum": [
        "flow",
        "security",
        "design",
        "performance",
        "seo",
        "domain",
        "compliance",
        "uptime"
      ],
      "description": "Run only this group's enabled monitors (as the dashboard's Run group): uptime = uptime, heartbeats and port monitors; flow = user flows; security; design; performance; seo; domain; compliance = legal compliance (accessibility)"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

cancel_queued_runs

Stop a site's runs that are queued but haven't started (after a big trigger_scan, or before maintenance). Cancelled runs can't be brought back: start them again with trigger_scan. The run that's already going finishes; nothing already recorded is deleted. Get the user's go-ahead first.

Parameters1

siteId

string

required

The site id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

request_ai_fix

Ask Relvato's AI to suggest a fix for a run that failed or found a problem (the dashboard's "Suggest a fix"). It answers in a minute or two: read it as aiFix on get_run. Plan-gated. get_fix_prompt gives the same brief for you to reason with yourself, without waiting.

Parameters1

runId

string

required

The run id

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "The run id"
    }
  },
  "required": [
    "runId"
  ],
  "additionalProperties": false
}

apply_fix

WordPress sites: apply the one-click fix a run proposes (get_run proposedFix: e.g. clear a stuck maintenance file, turn indexing back on, roll back the plugin update that broke it) through the Relvato plugin, then re-run the monitor to confirm. Only that exact fix can be applied. Tell the user what it changes (proposedFix.why and undo) and get their go-ahead first. undo: true reverts the last fix Relvato applied on the site. With Relvato plugin 1.77.0+ Relvato never changes the site remotely: the answer is applyInWordPress, a link where an administrator applies it in WordPress — give it to the user.

Parameters2

runId	string	required	The run that proposes the fix
undo	boolean	optional	Revert the last fix applied on this site instead

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "The run that proposes the fix"
    },
    "undo": {
      "type": "boolean",
      "description": "Revert the last fix applied on this site instead"
    }
  },
  "required": [
    "runId"
  ],
  "additionalProperties": false
}

start_safe_update

WordPress sites: for a vulnerable or outdated plugin a run found (get_run warnings with a plugin), update it (or deactivate it) through the Relvato plugin, re-run the monitors that were passing, and undo it automatically if any of them breaks. Counts as runs. Follow it with get_safe_update. Get the user's go-ahead first. With Relvato plugin 1.77.0+ the change is made in WordPress by an administrator (answer: applyInWordPress, a link to give the user); Relvato verifies it, and a change that breaks a monitor is undone there too.

Parameters3

runId	string	required	The run that found the plugin
plugin	string	required	The plugin's slug (the finding's subject.slug)
action	string	required

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "The run that found the plugin"
    },
    "plugin": {
      "type": "string",
      "description": "The plugin's slug (the finding's subject.slug)"
    },
    "action": {
      "type": "string",
      "enum": [
        "update",
        "deactivate"
      ]
    }
  },
  "required": [
    "runId",
    "plugin",
    "action"
  ],
  "additionalProperties": false
}

start_quarantine

After a hack or a cleanup (WordPress, paid plans): run the security monitors every hour for 48 hours, pause plugin updates (with Relvato plugin 1.77.0+ that pause is a tick box in WordPress → Relvato), and alert on every unexpected change. Uses runs (get_quarantine says how many). Stopping it early stays in the dashboard.

Parameters1

siteId

string

required

The site id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

extend_quarantine

Keep quarantine mode on for another 48 hours from now.

Parameters1

siteId

string

required

The site id

Raw schema

{
  "type": "object",
  "properties": {
    "siteId": {
      "type": "string",
      "description": "The site id"
    }
  },
  "required": [
    "siteId"
  ],
  "additionalProperties": false
}

send_test_alert

Send a test alert on one channel (email, slack or webhook) to check it arrives. Slack and webhooks are on paid plans and must be set up in the dashboard.

Parameters1

channel

string

required

Raw schema

{
  "type": "object",
  "properties": {
    "channel": {
      "type": "string",
      "enum": [
        "email",
        "slack",
        "webhook"
      ]
    }
  },
  "required": [
    "channel"
  ],
  "additionalProperties": false
}

resume_webhook

Turn webhook alerts back on after Relvato paused them for repeated failed deliveries (fix the endpoint first; send_test_alert checks it).

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

report_false_positive

Tell Relvato's team a run's result is wrong (it failed or warned about something that's fine). Sends the run's details and your note to Relvato's support team; it changes nothing on the run. To stop being told about a finding, use ignore_finding.

Parameters2

runId	string	required	The run id
note	string	optional	What's wrong with the result (optional)

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "The run id"
    },
    "note": {
      "type": "string",
      "description": "What's wrong with the result (optional)"
    }
  },
  "required": [
    "runId"
  ],
  "additionalProperties": false
}

ignore_finding

Stop a finding (a warning on a run, by its key from get_run) from counting on this monitor: it stays on the run, marked ignored, but no longer alerts or fails later runs. Undo with unignore_finding. Only do this when the user says the finding is expected.

Parameters2

runId	string	required	The run the finding is on
key	string	required	The finding's key (get_run warnings[].key)

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "The run the finding is on"
    },
    "key": {
      "type": "string",
      "description": "The finding's key (get_run warnings[].key)"
    }
  },
  "required": [
    "runId",
    "key"
  ],
  "additionalProperties": false
}

unignore_finding

Make an ignored finding count again (get_check lists a monitor's ignored findings with their keys; get_run marks them on a run).

Parameters3

checkId	string	required	The monitor
key	string	required	The finding's key
runId	string	optional	Optional: apply it to this run right away

Raw schema

{
  "type": "object",
  "properties": {
    "checkId": {
      "type": "string",
      "description": "The monitor"
    },
    "key": {
      "type": "string",
      "description": "The finding's key"
    },
    "runId": {
      "type": "string",
      "description": "Optional: apply it to this run right away"
    }
  },
  "required": [
    "checkId",
    "key"
  ],
  "additionalProperties": false
}

accept_visual_change

The visual monitor found a page that changed on purpose (a redesign, new content): make this run's screenshot the new baseline for that page, device and browser. Undo with undo_visual_review. Only when the user confirms the change is intended.

Parameters1

comparisonId

string

required

From get_run visualComparisons[].comparisonId

Raw schema

{
  "type": "object",
  "properties": {
    "comparisonId": {
      "type": "string",
      "description": "From get_run visualComparisons[].comparisonId"
    }
  },
  "required": [
    "comparisonId"
  ],
  "additionalProperties": false
}

ignore_visual_change

Ignore the area that changed on this comparison from now on (a clock, a rotating banner): it's added to the baseline's ignored regions. Undo with undo_visual_review. A mask (update_visual_monitor) is often the better fix.

Parameters1

comparisonId

string

required

From get_run visualComparisons[].comparisonId

Raw schema

{
  "type": "object",
  "properties": {
    "comparisonId": {
      "type": "string",
      "description": "From get_run visualComparisons[].comparisonId"
    }
  },
  "required": [
    "comparisonId"
  ],
  "additionalProperties": false
}

flag_visual_change_as_problem

The AI review let a visual change pass, but it's actually broken: mark it a failure. The run counts as failed in Relvato and shows as needing attention (notifications, Monitors passing); no message is sent.

Parameters1

comparisonId

string

required

From get_run visualComparisons[].comparisonId

Raw schema

{
  "type": "object",
  "properties": {
    "comparisonId": {
      "type": "string",
      "description": "From get_run visualComparisons[].comparisonId"
    }
  },
  "required": [
    "comparisonId"
  ],
  "additionalProperties": false
}

undo_visual_review

Undo the last accept or ignore on this page, device and browser: the earlier baseline comes back.

Parameters1

comparisonId

string

required

From get_run visualComparisons[].comparisonId

Raw schema

{
  "type": "object",
  "properties": {
    "comparisonId": {
      "type": "string",
      "description": "From get_run visualComparisons[].comparisonId"
    }
  },
  "required": [
    "comparisonId"
  ],
  "additionalProperties": false
}

accept_structure_change

The structure monitor found a page whose layout changed on purpose: adopt this run's structure as the new baseline for that page (pageKey), or for every changed page on the run (all: true). Undo with undo_structure_review.

Parameters3

runId	string	required	The structure monitor's run
pageKey	string	optional	The page (get_run metrics.pages[].pageKey)
all	boolean	optional	Every changed page on the run

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "The structure monitor's run"
    },
    "pageKey": {
      "type": "string",
      "description": "The page (get_run metrics.pages[].pageKey)"
    },
    "all": {
      "type": "boolean",
      "description": "Every changed page on the run"
    }
  },
  "required": [
    "runId"
  ],
  "additionalProperties": false
}

ignore_structure_change

Ignore specific element changes on a page from now on (signatures from get_run metrics.pages[].added / removed / countChanges[].sig), e.g. a widget that comes and goes. Undo with undo_structure_review.

Parameters3

runId	string	required	The run
pageKey	string	required	The page
signatures	array	required

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "The run"
    },
    "pageKey": {
      "type": "string",
      "description": "The page"
    },
    "signatures": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1
    }
  },
  "required": [
    "runId",
    "pageKey",
    "signatures"
  ],
  "additionalProperties": false
}

undo_structure_review

Undo the last accept or ignore on a page of the structure monitor.

Parameters2

runId	string	required	The run
pageKey	string	required	The page

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "The run"
    },
    "pageKey": {
      "type": "string",
      "description": "The page"
    }
  },
  "required": [
    "runId",
    "pageKey"
  ],
  "additionalProperties": false
}

README.md19 KBView on GitHub

Relvato

Relvato MCP server

Website monitoring your AI agent can run: add a site, set up and tune its monitors, run them, explain what broke and fix it with you.
Developer docs · Official MCP Registry · relvato.com

Relvato monitors websites in a real browser. It checks sign-ups, logins, checkout, payments, page speed, search visibility and security, and re-checks them every time the site changes. It works on any website and goes deepest on WordPress & WooCommerce.

This is Relvato's hosted Model Context Protocol server. There's nothing to install or run: point your MCP client at the URL and sign in to Relvato, or use a Relvato API key. This repository holds the connection details, the registry entry (server.json) and the Claude Code plugin (.claude-plugin/, skills/). The server itself runs at Relvato.


Endpoint	`https://app.relvato.com/api/mcp`
Transport	Streamable HTTP (stateless JSON-RPC over POST)
Auth	Sign in (OAuth 2.1: PKCE, Client ID Metadata Documents, resource indicators), or an API key: `Authorization: Bearer rlv_…`
Registry name	`com.relvato/relvato`

Sign-in works in clients that identify themselves with a Client ID Metadata Document (CIMD): Claude (claude.ai, Desktop, and Claude Code 2.1.81 or later), ChatGPT and VS Code. Relvato doesn't offer dynamic client registration, so a client that can only register itself that way (Cursor for now, the Gemini CLI, Docker's MCP gateway), or that has no sign-in at all (DeepSeek Harness), uses an API key instead.

In a client that supports it, add the endpoint with nothing else. The first time the client uses it, it opens Relvato's sign-in:

Sign up (there's a free plan) or sign in.
Allow the client to read your sites and results and to make changes: add and configure sites and monitors, change schedules and run scans.
If you belong to an organization, pick which of its workspaces to connect. Your personal workspace isn't offered there, so use an API key for it.

Discovery follows the MCP authorization spec. A 401 points to /.well-known/oauth-protected-resource/api/mcp, and the authorization server is https://clerk.relvato.com (client_id_metadata_document_supported; no registration endpoint). The scopes are relvato:read, relvato:write and user:org:read.

Or use an API key

For scripts, for clients that can't sign in (no CIMD support), or for your personal workspace while you're in an organization:

Open API access from the account menu, or go to app.relvato.com/api-access.
Create a key:
- Full access lets the agent add and configure sites and monitors, run them, review results and apply the fixes runs propose.
- Read-only lets it read everything: sites, health and uptime, performance, runs, monitors, WordPress updates and activity, fix briefs and alert settings. With a read-only key the client only sees the read tools.
Send it as Authorization: Bearer rlv_… (or x-api-key: rlv_…). A key is shown once. Keep it out of files you commit.

Connect

Claude (claude.ai, Desktop, mobile)

Settings → Connectors → Add custom connector. Enter the URL https://app.relvato.com/api/mcp, then Connect and sign in.

Claude Code

The plugin (recommended): the server plus three skills for working from a code repo.

bash

claude plugin marketplace add Relvato/relvato-mcp
claude plugin install relvato@relvato

Then run /mcp, choose plugin:relvato:relvato, then Authenticate. The skills:

Skill	What it does
`/relvato:setup [url]`	Adds the site this repo deploys, proves ownership (it can add the verification meta tag to your code), picks monitors for what matters and starts the first runs.
`/relvato:check-after-deploy [site] [group]`	Runs the site's monitors after a deploy, says how long they'll take, and reports what passed and what broke, with links. Only runs when you type it, since runs use your monthly quota.
`/relvato:fix-failure [run]`	Reads a failed run and its fix brief, finds the cause in the code (including what changed since it last passed), makes the smallest fix with your OK, then re-runs that monitor.

Already added Relvato on claude.ai? With a Claude subscription, that connector shows up in Claude Code too. The skills work with either connection.

Just the server:

bash

claude mcp add --transport http relvato https://app.relvato.com/api/mcp

Then run /mcp, choose relvato, then Authenticate. With an API key instead:

bash

claude mcp add --transport http relvato https://app.relvato.com/api/mcp --header "Authorization: Bearer rlv_your_key"

Cursor

In ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project), with an API key. Cursor doesn't support Client ID Metadata Documents yet, so it can't use Relvato's sign-in:

json

{
  "mcpServers": {
    "relvato": {
      "url": "https://app.relvato.com/api/mcp",
      "headers": {
        "Authorization": "Bearer rlv_your_key"
      }
    }
  }
}

Once Cursor supports CIMD, the URL alone will be enough: Cursor will offer to sign in.

VS Code

In .vscode/mcp.json. VS Code offers to sign in:

json

{
  "servers": {
    "relvato": {
      "type": "http",
      "url": "https://app.relvato.com/api/mcp"
    }
  }
}

With an API key, VS Code can ask for it once and store it securely, so it never sits in the file:

json

{
  "inputs": [
    { "type": "promptString", "id": "relvato-key", "description": "Relvato API key (rlv_…)", "password": true }
  ],
  "servers": {
    "relvato": {
      "type": "http",
      "url": "https://app.relvato.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:relvato-key}"
      }
    }
  }
}

Gemini CLI

Install the extension from this repository:

bash

gemini extensions install https://github.com/Relvato/relvato-mcp

It asks for your Relvato API key (create one) and keeps it in your system keychain; it never sits in a file. To change it later: gemini extensions config relvato. The Gemini CLI can't use Relvato's sign-in (it supports only dynamic client registration, which Relvato doesn't offer), so the extension uses the key.

Without the extension, add the server to ~/.gemini/settings.json:

json

{
  "mcpServers": {
    "relvato": {
      "httpUrl": "https://app.relvato.com/api/mcp",
      "headers": {
        "Authorization": "Bearer rlv_your_key"
      }
    }
  }
}

DeepSeek Harness

Add the dsh-plugin-relvato bundle to a profile, with your API key in RELVATO_API_KEY (your environment or ~/.dsh/.env):

bash

dsh plugin --profile web add dsh-plugin-relvato

It's on npm; github:Relvato/dsh-plugin-relvato installs it straight from GitHub.

dsh's MCP client sends headers and has no sign-in, so it uses the key. The tools appear as mcp__relvato__<tool>.

Cline

In cline_mcp_settings.json (MCP Servers → Configure), with an API key:

json

{
  "mcpServers": {
    "relvato": {
      "type": "streamableHttp",
      "url": "https://app.relvato.com/api/mcp",
      "headers": {
        "Authorization": "Bearer rlv_your_key"
      }
    }
  }
}

Agents that set servers up themselves can follow llms-install.md.

Any other client

Add a remote HTTP (streamable HTTP) server with the endpoint above. If the client supports MCP sign-in with Client ID Metadata Documents (CIMD), that's all. Otherwise (including clients that only do dynamic client registration) add an Authorization: Bearer rlv_… header. In the common mcp.json format:

json

{
  "mcpServers": {
    "relvato": {
      "type": "http",
      "url": "https://app.relvato.com/api/mcp",
      "headers": {
        "Authorization": "Bearer rlv_your_key"
      }
    }
  }
}

Tools

57 tools, grouped by job in the order tools/list sends them. read tools work with any connection; full access tools need a full-access key, or a sign-in that allowed changes.

Set up

Tool	What it does	Access needed
`list_sites`	List the account's websites and whether each is ready to run monitors.	read
`add_site`	Add a website and get its setup step: connect the WordPress plugin, or verify the domain.	full access
`verify_site`	Check that setup step: the plugin connection, or the domain-verification DNS record or meta tag.	full access
`start_monitoring_for_goals`	Pick what matters (checkout, security, search, speed, …) and get the monitors that cover it on your plan.	full access
`list_checks`	The monitors you can add to a site: what each catches, whether your plan includes it, and which are recommended.	read
`add_checks`	Add monitors to a site; each one reports added, already there, or why not.	full access
`dismiss_recommendation`	Stop recommending a monitor for a site, or bring dismissed recommendations back.	full access
`calibrate_site`	WooCommerce: read the store again (a product to buy, checkout type, currency) after it changed.	full access
`verify_vitals_beacon`	Check the real-user Web Vitals beacon is installed.	full access

Read

Tool	What it does	Access needed
`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.	read
`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.	read
`get_performance`	Lab and real-user Core Web Vitals, what slows the site down, and the top fixes with steps.	read
`get_check`	One monitor in full: schedule, its own settings (pages, masks, checkout details, …), ignored findings, its recipe if AI-written, latest run.	read
`list_runs`	Recent runs, newest first — by site, monitor or status, with paging.	read
`get_run`	One run in detail: steps, findings, visual comparisons with image links, the fix it proposes, plugins it can update.	read
`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.	read
`get_updates`	WordPress: auto-update windows and what they updated or rolled back, held versions, safe updates, hardening.	read
`get_safe_update`	Follow a safe plugin update or deactivation until it passes or is undone.	read
`get_quarantine`	Quarantine mode: available or not, on until when, every change it saw, past sessions.	read
`get_activity_log`	WordPress: sign-ins, failed sign-ins, accounts, updates, settings and file edits, within your plan's history.	read
`get_notifications`	The dashboard's notifications: failing monitors, plugin or beacon problems, paused channels, billing.	read
`get_site_settings`	A site's settings — what an agent may change and what stays in the dashboard (never secret values).	read
`get_alert_settings`	Who is told about what: frequency, severity, each channel's state and routing — no URLs or secrets.	read
`get_status_pages`	Status pages and client reports: settings only, never a private link or recipients' addresses.	read
`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.	read

Tune

Tool	What it does	Access needed
`update_check`	Turn a monitor on or off, or change when it runs: schedule, re-runs on WordPress updates, random extra runs.	full access
`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.	full access
`resume_monitor_group`	Resume a paused group now; a monitor the plan no longer allows stays off, with the reason.	full access
`update_visual_monitor`	Add pages of your own by address to the visual monitor, set masks, devices, browsers and the threshold.	full access
`update_check_settings`	A monitor's own settings: checkout details, extra pages to scan, what the site's AI feature must answer, DKIM selectors, …	full access
`add_custom_check`	Describe what must be true on a page; Relvato's AI writes the monitor.	full access
`edit_custom_check`	Give a custom monitor a new goal or page; the AI writes a new recipe to approve.	full access
`reauthor_custom_check`	Answer the AI's question, or have it write a custom monitor's recipe again.	full access
`approve_custom_check`	Approve a proposed recipe so the custom monitor runs (interactive recipes need an explicit OK).	full access
`update_site_settings`	Pacing, spacing between runs, firewall retry, flaky-monitor recovery, plugin rollback.	full access
`update_alert_settings`	Alert timing and minimum severity. Who receives alerts and muting stay in the dashboard.	full access
`add_heartbeat`	Create a heartbeat for a cron job or backup and get the URL the job requests when it succeeds.	full access
`update_heartbeat`	Rename, reschedule, pause or resume a heartbeat. Deleting stays in the dashboard.	full access

Run and act

Tool	What it does	Access needed
`trigger_scan`	Run a site's monitors now — all, one group, or one monitor — and get the run ids back (uses the monthly quota).	full access
`cancel_queued_runs`	Stop a site's queued runs; the one already going finishes.	full access
`request_ai_fix`	Ask Relvato's AI for a fix suggestion for a failed run (paid plans).	full access
`apply_fix`	WordPress: apply the one-click fix a run proposes — only that fix — then re-run the monitor.	full access
`start_safe_update`	WordPress: update or deactivate a vulnerable plugin, re-check, and undo it if anything breaks.	full access
`start_quarantine`	After a hack: hourly security runs for 48 hours with plugin updates paused.	full access
`extend_quarantine`	Keep quarantine mode on for another 48 hours.	full access
`send_test_alert`	Send a test alert by email, Slack or webhook.	full access
`resume_webhook`	Turn webhook alerts back on after Relvato paused them for failed deliveries.	full access
`report_false_positive`	Tell Relvato's team a result is wrong; it changes nothing on the run.	full access

Review results

Tool	What it does	Access needed
`ignore_finding`	Stop a finding from counting on a monitor (undoable). Only when you confirm it's expected.	full access
`unignore_finding`	Make an ignored finding count again.	full access
`accept_visual_change`	Make this run's screenshot the new baseline for a page (undoable).	full access
`ignore_visual_change`	Ignore the area that changed on a page from now on (undoable).	full access
`flag_visual_change_as_problem`	Mark a visual change the AI let pass as a failure.	full access
`undo_visual_review`	Undo the last visual accept or ignore.	full access
`accept_structure_change`	Adopt a page's new structure as its baseline (undoable).	full access
`ignore_structure_change`	Ignore specific element changes on a page (undoable).	full access
`undo_structure_review`	Undo the last structure accept or ignore.	full access

initialize and tools/list answer without signing in, so directories and clients can show what the server offers. Every tool call needs a sign-in or a key. A read-only key, or a sign-in without write access, gets only the read tools.

Things to ask

"Set up monitoring for example.com and tell me what I need to do to connect it."
"Add my pricing and blog pages to the visual monitor, and run it."
"Why did checkout fail on my shop last night, and how do I fix it?" (and, once you agree, "apply that fix")
"How fast is my shop for real visitors, and what's slowing it down?"
"The homepage redesign is intentional: accept the new screenshots."
"Who signed in to WordPress this week, and did anyone fail to?"
"Write a monitor that checks the Pro plan still shows a price."

What an agent can't do

The agent works under the same rules as the dashboard. Some things stay in the dashboard, with a person looking:

Skip ownership. A new site runs no monitors until its WordPress plugin is connected or its domain is verified.
Silence something for good. It can accept or ignore a result only in ways that can be undone, and only when you confirm the change is intended. Approving file-integrity, script and DNS changes (no undo; exactly what an attacker wants clicked) stays in the dashboard.
Change your site beyond what a run proposes. On WordPress it applies only the one-click fix a run proposes, and updates or deactivates a vulnerable plugin only with automatic undo. Destructive tools are marked, so your client asks you first.
Weaken alerts or protection. Who receives alerts, muting, stopping quarantine mode, the proxy and the firewall token stay in the dashboard.
Touch secrets. Connect tokens, signing secrets, webhook URLs and report share links are never exposed.
Delete anything, or change billing.
Go past your plan. Plan limits apply exactly as in the dashboard.

Limits

Requests are rate-limited per workspace, per minute, counted across the REST API and MCP together, whether you sign in or use a key:

Plan	Requests per minute
Free	30
Pro	120
Business	600
Agency	2,400

Runs started with trigger_scan (and the runs that confirm apply_fix and start_safe_update) count toward the same monthly run quota as scheduled runs. See pricing.

Also available

REST API. The same read data at https://app.relvato.com/api/v1 (sites, health, performance, runs, monitors, updates, activity, notifications), using the same keys. See the developer docs.
Webhooks. A signed JSON event for every alert (Pro and up).

Support

Questions and bug reports: relvato.com/contact, or open an issue here.
Service status: relvato.com/status.
Security issues: please use the contact page, not a public issue.

This repository contains documentation and configuration only. The Relvato service is proprietary and covered by its terms. The contents of this repository are MIT-licensed (see LICENSE), so copy the config snippets freely.

Install

Tools (57)

list_sitesadd_siteverify_sitestart_monitoring_for_goalslist_checksadd_checksdismiss_recommendationcalibrate_site

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://app.relvato.com/api/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "relvato": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.relvato.com/api/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

Model Context Protocol (MCP) Server: com.relvato/relvato

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

list_sites

add_site

verify_site

start_monitoring_for_goals

list_checks

add_checks

dismiss_recommendation

calibrate_site

verify_vitals_beacon

site_overview

get_site_health

get_performance

get_check

list_runs

get_run

get_fix_prompt

get_updates

get_safe_update

get_quarantine

get_activity_log

get_notifications

get_site_settings

get_alert_settings

get_status_pages

list_heartbeats

update_check

pause_monitor_group

resume_monitor_group

update_visual_monitor

update_check_settings

add_custom_check

edit_custom_check

reauthor_custom_check

approve_custom_check

update_site_settings

update_alert_settings

add_heartbeat

update_heartbeat

trigger_scan

cancel_queued_runs

request_ai_fix

apply_fix

start_safe_update

start_quarantine

extend_quarantine

send_test_alert

resume_webhook

report_false_positive

ignore_finding

unignore_finding

accept_visual_change

ignore_visual_change

flag_visual_change_as_problem

undo_visual_review

accept_structure_change

ignore_structure_change

undo_structure_review

Relvato MCP server

Sign in (no key needed)

Or use an API key

Connect

Claude (claude.ai, Desktop, mobile)

Claude Code

Cursor

VS Code

Gemini CLI

DeepSeek Harness

Cline

Any other client

Tools

Set up

Read

Tune

Run and act