Connect Relvato and your agent gets 58 tools, among them accept_structure_change, accept_visual_change, add_checks. It answers at https://app.relvato.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 28 September 2026; the last check, on 14 November 2026, succeeded.
Website monitoring: add sites, configure and run monitors, read health, review results, apply fixes.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: runId, pageKey, all |
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 intend Inputs: comparisonId |
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 Inputs: siteId, keys |
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 → propo Inputs: siteId, url, goal, name, authenticated, interactive |
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 repor Inputs: siteId, name, periodSec, cron, tz, graceSec |
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 Inputs: url, name, platform |
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 conf Inputs: runId, undo |
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 th Inputs: checkId, ack |
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 sa Inputs: runId |
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. Inputs: siteId |
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 recor Inputs: siteId |
dismiss_recommendation | Stop recommending a monitor for a site (list_checks marks recommendations), or bring every dismissed recommendation back with restoreAll. Inputs: siteId, key, restoreAll |
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. Inputs: checkId, url, goal, name, authenticated, interactive |
extend_quarantine | Keep quarantine mode on for another 48 hours from now. Inputs: siteId |
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. Inputs: comparisonId |
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 f Inputs: siteId, filter, search, days, limit |
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 |
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 t Inputs: checkId |
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 finding Inputs: runId |
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_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 Inputs: siteId |
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 wou Inputs: siteId |
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 Inputs: runId |
get_safe_update | Follow a safe update or deactivation: applying → verifying → passed, or reverted with the monitors that broke. Inputs: changeId |
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 f Inputs: siteId, range |
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 Inputs: siteId |
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' |
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 harde Inputs: siteId |
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 findi Inputs: runId, key |
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. Inputs: runId, pageKey, signatures |
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. Inputs: comparisonId |
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 no Inputs: siteId |
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 Inputs: siteId |
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 Inputs: siteId, checkId, status, before, limit |
list_sites | List the websites in this Relvato account, with whether each is ready to run monitors. |
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 Inputs: siteId, group, duration |
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. Inputs: checkId, answer |
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_fi Inputs: runId, note |
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 Inputs: runId |
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. Inputs: siteId, group |
resume_webhook, send_test_alert, site_overview, start_monitoring_for_goals, start_quarantine, start_safe_update, trigger_scan, undo_structure_review, undo_visual_review, unignore_finding, update_alert_settings, update_check, update_check_settings, update_heartbeat, update_site_settings, update_visual_monitor, verify_site, verify_vitals_beacon
Every block below points at https://app.relvato.com/api/mcp. Pick your client and copy.
claude mcp add --transport http relvato https://app.relvato.com/api/mcp
{
"mcpServers": {
"relvato": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://app.relvato.com/api/mcp"]
}
}
}{
"mcpServers": {
"relvato": {
"url": "https://app.relvato.com/api/mcp"
}
}
}{
"servers": {
"relvato": {
"type": "http",
"url": "https://app.relvato.com/api/mcp"
}
}
}{
"context_servers": {
"relvato": {
"url": "https://app.relvato.com/api/mcp"
}
}
}{
"mcpServers": {
"relvato": {
"serverUrl": "https://app.relvato.com/api/mcp"
}
}
}{
"mcpServers": {
"relvato": {
"url": "https://app.relvato.com/api/mcp"
}
}
}name: Relvato
version: 0.0.1
schema: v1
mcpServers:
- name: Relvato
type: streamable-http
url: https://app.relvato.com/api/mcp{
"mcpServers": {
"relvato": {
"httpUrl": "https://app.relvato.com/api/mcp"
}
}
}{
"mcpServers": {
"relvato": {
"type": "http",
"url": "https://app.relvato.com/api/mcp"
}
}
}{
"mcpServers": {
"relvato": {
"url": "https://app.relvato.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapp.relvato.com%2Fapi%2Fmcp&type=streamable_http&id=relvato&name=Relvato
It answered our last check on 14 November 2026 in 139 ms. Over 4 checks since 28 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by relvato.com and served from app.relvato.com, the vendor's own domain: https://app.relvato.com/api/mcp.
58, as returned by the server's own tools/list on 17 November 2026: accept_structure_change, accept_visual_change, add_checks, add_custom_check, add_heartbeat, add_site, apply_fix, approve_custom_check, and 50 more.
It answered our last check on 14 November 2026 in 139 ms. Over 4 checks since 28 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://app.relvato.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.relvato. Endpoint host: app.relvato.com. ARD identifier: urn:air:com.relvato:mcp:relvato.
First indexed 28 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.