Name: Relvato
Author: com.relvato

Tools observed via MCP handshake

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 the setup step the owner must complete before any monitor runs: connect the WordPress plugin, or verify the dom
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 (met
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 struc
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 alr
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 pl
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 back
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 sta
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
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),
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 sett
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, trig
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
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 mon
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 rollb
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, e
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
get_notifications — The dashboard's notifications: failing monitors, a disconnected or outdated WordPress plugin, a silent real-user beacon, domain and ownership problems, safe upd
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
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, wh
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.
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,
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 whe
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
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)
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),
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 a
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
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
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 s
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 recip
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, an
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. On
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. `
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
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 q
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
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
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 u
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-r
start_quarantine — After a hack or a cleanup (WordPress, paid plans): run the security monitors every hour for 48 hours, pause plugin updates, and alert on every unexpected change
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;
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 l
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).
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
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_re
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 (notific
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
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 a
undo_structure_review — Undo the last accept or ignore on a page of the structure monitor.

when	check	result	http	latency	detail
31 min ago	mcp initialize	ok	200	73 ms	server relvato 3.2.0 · protocol 2025-06-18 · 57 tools
7 h ago	mcp initialize	ok	200	58 ms	server relvato 3.2.0 · protocol 2025-06-18 · 57 tools
13 h ago	mcp initialize	ok	200	104 ms	server relvato 3.2.0 · protocol 2025-06-18 · 57 tools
20 h ago	mcp initialize	ok	200	163 ms	server relvato 3.2.0 · protocol 2025-06-18 · 57 tools
27 h ago	mcp initialize	ok	200	75 ms	server relvato 3.2.0 · protocol 2025-06-18 · 57 tools
33 h ago	mcp initialize	ok	200	64 ms	server relvato 3.2.0 · protocol 2025-06-18 · 57 tools
2 d ago	mcp initialize	ok	200	48 ms	server relvato 3.2.0 · protocol 2025-06-18 · 57 tools
2 d ago	mcp initialize	ok	200	62 ms	server relvato 3.2.0 · protocol 2025-06-18 · 57 tools
2 d ago	mcp initialize	ok	200	64 ms	server relvato 3.2.0 · protocol 2025-06-18 · 57 tools
3 d ago	mcp initialize	ok	200	64 ms	server relvato 3.2.0 · protocol 2025-06-18 · 57 tools

Relvato

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from