# Relvato

- Registry name: `com.relvato/relvato` · version 3.5.0
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.relvato%2Frelvato
- Server page: https://mcpstation.net/s/com.relvato--relvato.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://app.relvato.com/api/mcp`

## Tools (as reported by the server, not verified)

- `list\_sites`: List the websites in this Relvato account, with whether each is ready to run monitors.
- `add\_site`: Start monitoring a website. Returns the site and its setup: until the owner proves ownership \(connect the WordPress plugin, or verify the domain — the only option for non-WordPress sites\), trigger\_scan can run the public monitors by hand 3 times a day \(setup.manualRuns\); scheduled runs, alerts, upda
- `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/verif
- `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, cust
- `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. Before the site's ownership is proven, runsNow says which can run now \(started by hand\) and which after proof; for a site added
- `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\). Once the site's ownership is proven, new monitors get a daily schedule on plans that run daily \(Pro and up\) and a weekly one on Free,
- `dismiss\_recommendation`: Stop recommending a monitor for a site \(list\_checks marks recommendations\), or bring every dismissed recommendation back with restoreAll.
- `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.
- `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.
- `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 Abil
- `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
- `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.
- `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
- `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\).
- `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
- `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 /
- `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.
- `get\_safe\_update`: Follow a safe update or deactivation: applying → verifying → passed, or reverted with the monitors that broke.
- `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.
- `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\).
- `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.
- `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, firewal
- `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
- `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.
- `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 fa
- `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 fiel
- `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. Pausi
- `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.
- `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\), re
- `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 s
- `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\_cus
- `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.
- `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.
- `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.
- `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.
- `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 s
- `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 wit
- `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.
- `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 resul
- `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.
- `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.
- `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
- `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 if any of them breaks. Counts as runs. Follow it with get\_safe\_update. Get the user's go-ahea
- `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
- `extend\_quarantine`: Keep quarantine mode on for another 48 hours from now.
- `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.
- `resume\_webhook`: Turn webhook alerts back on after Relvato paused them for repeated failed deliveries \(fix the endpoint first; send\_test\_alert checks it\).
- `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.
- `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.
- `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\).
- `bring\_back\_run`: Relvato AI triage \(a site on level "aside"\) set this failed run aside as likely noise — get\_run shows aiTriage.setAside. Make it count as a failure again: in the bell, the digest and site health. No alert is re-sent. Use it when the user says the failure is real.
- `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.
- `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.
- `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.
- `undo\_visual\_review`: Undo the last accept or ignore on this page, device and browser: the earlier baseline comes back.
- `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.
- `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.
- `undo\_structure\_review`: Undo the last accept or ignore on a page of the structure monitor.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html