com.relvato/relvato

Est-ce que com.relvato/relvato est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.relvato/relvato » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 58 outils

• accept_structure_change≈ 203 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "accept_structure_change", "arguments": {"runId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• accept_visual_change≈ 172 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • comparisonId · string · requis
    From get_run visualComparisons[].comparisonId

  Exemple d'appel

  {"name": "accept_visual_change", "arguments": {"comparisonId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_checks≈ 259 tokens

  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, plus a re-run when the site changes on Pro and up (WordPress plugin updates, or pushes via the GitHub App). Before proof they're added but only run when trigger_scan starts them (scheduleStarts).

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "add_checks", "arguments": {"keys": [], "siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_custom_check≈ 358 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

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

  Exemple d'appel

  {"name": "add_custom_check", "arguments": {"url": "texte", "goal": "texte", "siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_heartbeat≈ 417 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • tz · string · optionnel
    The cron expression's IANA time zone, e.g. Europe/Bucharest (default UTC)
  • cron · string · optionnel
    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
  • name · string · requis
    What the job is, e.g. "Nightly backup"
  • siteId · string · requis
    The site's id
  • graceSec · number · optionnel
    How late a ping may be before it counts as missed, in seconds (60 to 604800 = 7 days; default 3600)
  • periodSec · number · optionnel
    How often the job runs, in seconds (60 to 2678400 = 31 days; default 86400 = daily). Ignored when `cron` is set

  Exemple d'appel

  {"name": "add_heartbeat", "arguments": {"name": "texte", "siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_site≈ 342 tokens

  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, update/deploy runs and the monitors that act on the site need the proof (setup.nextStep); setup.afterProof says what proof adds for this site on its plan. 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

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "add_site", "arguments": {"url": "texte", "platform": "wordpress"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• apply_fix≈ 277 tokens

  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 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • undo · boolean · optionnel
    Revert the last fix applied on this site instead
  • runId · string · requis
    The run that proposes the fix

  Exemple d'appel

  {"name": "apply_fix", "arguments": {"runId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• approve_custom_check≈ 204 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "approve_custom_check", "arguments": {"checkId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• bring_back_run≈ 170 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • runId · string · requis
    The set-aside run

  Exemple d'appel

  {"name": "bring_back_run", "arguments": {"runId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• calibrate_site≈ 138 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "calibrate_site", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cancel_queued_runs≈ 169 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "cancel_queued_runs", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dismiss_recommendation≈ 192 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • key · string · optionnel
    The monitor key to stop recommending
  • siteId · string · requis
    The site id
  • restoreAll · boolean · optionnel
    true: bring back every recommendation dismissed on this site (key not needed)

  Exemple d'appel

  {"name": "dismiss_recommendation", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• edit_custom_check≈ 264 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • url · string · requis
    The page to check: a full URL on the site
  • goal · string · requis
    What must be true on that page
  • name · string · optionnel
    A new name
  • checkId · string · requis
    The custom monitor's id
  • interactive · boolean · optionnel
    Allow clicking and typing on the live page (search, filters, forms)
  • authenticated · boolean · optionnel
    WordPress sites: run logged in as Relvato's verification user

  Exemple d'appel

  {"name": "edit_custom_check", "arguments": {"url": "texte", "goal": "texte", "checkId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• extend_quarantine≈ 113 tokens

  Keep quarantine mode on for another 48 hours from now.

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "extend_quarantine", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• flag_visual_change_as_problem≈ 171 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • comparisonId · string · requis
    From get_run visualComparisons[].comparisonId

  Exemple d'appel

  {"name": "flag_visual_change_as_problem", "arguments": {"comparisonId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_activity_log≈ 318 tokens

  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).

  Paramètres, retour & exemple (5)

  Paramètres

  • days · number · optionnel
    How far back (up to the plan's history)
  • limit · number · optionnel
    Max events, 1-300 (default 100)
  • filter · string · optionnel · all | logins | people | changes | errors
    logins = sign-ins and failed sign-ins; people = roles, deleted accounts, application passwords; changes = plugin / theme / core updates, settings and file edits; errors = PHP errors and failed emails; all (default) = everything
  • search · string · optionnel
    Only events mentioning this (a username, a plugin)
  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "get_activity_log", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_alert_settings≈ 175 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_alert_settings", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_check≈ 231 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • checkId · string · requis
    The monitor's id (from site_overview or add_checks)

  Exemple d'appel

  {"name": "get_check", "arguments": {"checkId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_fix_prompt≈ 205 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • runId · string · requis
    The run id

  Exemple d'appel

  {"name": "get_fix_prompt", "arguments": {"runId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_notifications≈ 127 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_notifications", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_performance≈ 158 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "get_performance", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_quarantine≈ 158 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "get_quarantine", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_run≈ 232 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • runId · string · requis
    The run id

  Exemple d'appel

  {"name": "get_run", "arguments": {"runId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_safe_update≈ 127 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • changeId · string · requis
    From start_safe_update

  Exemple d'appel

  {"name": "get_safe_update", "arguments": {"changeId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_site_health≈ 209 tokens

  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).

  Paramètres, retour & exemple (2)

  Paramètres

  • range · number · optionnel · 28 | 90 | 182
    Trend length in days (default 28)
  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "get_site_health", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_site_settings≈ 202 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "get_site_settings", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_status_pages≈ 142 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_status_pages", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_updates≈ 162 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "get_updates", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ignore_finding≈ 186 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "ignore_finding", "arguments": {"key": "texte", "runId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ignore_structure_change≈ 223 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • runId · string · requis
    The run
  • pageKey · string · requis
    The page
  • signatures · array · requis
    The element signatures to ignore, from the run (get_run metrics.pages[].added / removed / countChanges[].sig)

  Exemple d'appel

  {"name": "ignore_structure_change", "arguments": {"runId": "texte", "pageKey": "texte", "signatures": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ignore_visual_change≈ 166 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • comparisonId · string · requis
    From get_run visualComparisons[].comparisonId

  Exemple d'appel

  {"name": "ignore_visual_change", "arguments": {"comparisonId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_checks≈ 185 tokens

  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 as "other", withWordPressPlugin lists what the WordPress plugin adds.

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "list_checks", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_heartbeats≈ 214 tokens

  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).

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site's id

  Exemple d'appel

  {"name": "list_heartbeats", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_runs≈ 266 tokens

  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).

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "list_runs", "arguments": {"limit": 1, "before": "texte", "siteId": "texte", "status": "passed", "checkId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_sites≈ 86 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_sites", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pause_monitor_group≈ 357 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "pause_monitor_group", "arguments": {"group": "flow", "siteId": "texte", "duration": "1h"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reauthor_custom_check≈ 188 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • answer · string · optionnel
    Your reply to the AI's question (get_check custom.question)
  • checkId · string · requis
    The custom monitor's id

  Exemple d'appel

  {"name": "reauthor_custom_check", "arguments": {"checkId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• report_false_positive≈ 183 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • note · string · optionnel
    What's wrong with the result (optional)
  • runId · string · requis
    The run id

  Exemple d'appel

  {"name": "report_false_positive", "arguments": {"runId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• request_ai_fix≈ 166 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • runId · string · requis
    The run id

  Exemple d'appel

  {"name": "request_ai_fix", "arguments": {"runId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resume_monitor_group≈ 202 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • group · string · requis · flow | security | design | performance | seo | domain | compliance | uptime
    The paused group (site_overview pausedGroups)
  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "resume_monitor_group", "arguments": {"group": "flow", "siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resume_webhook≈ 112 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "resume_webhook", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• send_test_alert≈ 152 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • channel · string · requis · email | slack | webhook
    Which channel to send the test alert on

  Exemple d'appel

  {"name": "send_test_alert", "arguments": {"channel": "email"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• site_overview≈ 215 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "site_overview", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• start_monitoring_for_goals≈ 274 tokens

  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. Before the site's ownership is proven the monitors are added but don't run on their schedule yet (scheduleStarts).

  Paramètres, retour & exemple (2)

  Paramètres

  • goals · array · requis
    What the user wants watched, one or more (see the list above)
  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "start_monitoring_for_goals", "arguments": {"goals": [], "siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• start_quarantine≈ 179 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "start_quarantine", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• start_safe_update≈ 311 tokens

  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-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 if it breaks a monitor Relvato alerts the user to undo it there.

  Paramètres, retour & exemple (3)

  Paramètres

  • runId · string · requis
    The run that found the plugin
  • action · string · requis · update | deactivate
    update: to the fixed (or latest) version; deactivate: switch the plugin off
  • plugin · string · requis
    The plugin's slug (the finding's subject.slug)

  Exemple d'appel

  {"name": "start_safe_update", "arguments": {"runId": "texte", "action": "update", "plugin": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• trigger_scan≈ 329 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • group · string · optionnel · flow | security | design | performance | seo | domain | compliance | uptime
    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)
  • siteId · string · requis
    The site id
  • checkId · string · optionnel
    Run only this monitor

  Exemple d'appel

  {"name": "trigger_scan", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• undo_structure_review≈ 134 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • runId · string · requis
    The run
  • pageKey · string · requis
    The page

  Exemple d'appel

  {"name": "undo_structure_review", "arguments": {"runId": "texte", "pageKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• undo_visual_review≈ 136 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • comparisonId · string · requis
    From get_run visualComparisons[].comparisonId

  Exemple d'appel

  {"name": "undo_visual_review", "arguments": {"comparisonId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• unignore_finding≈ 172 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • key · string · requis
    The finding's key
  • runId · string · optionnel
    Optional: apply it to this run right away
  • checkId · string · requis
    The monitor

  Exemple d'appel

  {"name": "unignore_finding", "arguments": {"key": "texte", "checkId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_alert_settings≈ 355 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • everyRun · boolean · optionnel
    Email every run, not only problems
  • timezone · string · optionnel
    IANA time zone for the digest, e.g. Europe/Berlin
  • frequency · array · optionnel
    When alerts go out: instant (as it happens), a daily digest, a weekly digest — one or more
  • digestTime · string · optionnel
    HH:MM (24h) for the daily / weekly digest
  • minSeverity · string · optionnel · warning | low | medium | high | critical
    Only alert on problems at least this serious
  • digestWeekday · number · optionnel
    Weekly digest day, 0 = Sunday … 6 = Saturday

  Exemple d'appel

  {"name": "update_alert_settings", "arguments": {"everyRun": true, "timezone": "texte", "frequency": [], "digestTime": "texte", "minSeverity": "warning", "digestWeekday": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_check≈ 484 tokens

  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.

  Paramètres, retour & exemple (8)

  Paramètres

  • at · string · optionnel
    Daily/weekly run time, HH:MM (24h)
  • tz · string · optionnel
    IANA timezone for `at`, e.g. Europe/Berlin
  • dow · number · optionnel
    Weekly only: weekday, 0 = Sunday … 6 = Saturday
  • events · array · optionnel
    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 · optionnel
    Random extra runs (times per days), with an off or weekly schedule; null turns them off
  • checkId · string · requis
    The monitor's id (from site_overview or add_checks)
  • enabled · boolean · optionnel
    Turn the monitor on or off
  • schedule · string · optionnel · off | weekly | daily | 6h | hourly | fastest
    Recurring schedule

  Exemple d'appel

  {"name": "update_check", "arguments": {"checkId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_check_settings≈ 2766 tokens

  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.

  Paramètres, retour & exemple (14)

  Paramètres

  • uptime · object · optionnel
    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)
  • checkId · string · requis
    The monitor's id
  • devices · array · optionnel
    Flow and page monitors
  • shopUrl · string · optionnel
    Prices: the shop page
  • aiOutput · object · optionnel
    The site's own AI feature: its endpoint (full URL on the site), a fixed prompt, and what the answer must (not) contain
  • checkout · object · optionnel
    Checkout monitors
  • browseUrl · string · optionnel
    Storefront: the shop page (blank = the calibrated one)
  • errorScan · object · optionnel
    Extra pages to scan (full URLs on the site) and error texts to ignore
  • productUrl · string · optionnel
    Prices: a sample product
  • brokenLinks · object · optionnel
    Extra pages to crawl, address fragments to skip, and whether external links are checked too
  • dkimSelectors · array · optionnel
    Email authentication: your mail provider's DKIM selectors (up to 10)
  • structurePages · array · optionnel
    Structure drift: pages to fingerprint
  • webVitalsDevices · array · optionnel
    Core Web Vitals: devices to measure
  • accessibilityPages · array · optionnel
    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

  Exemple d'appel

  {"name": "update_check_settings", "arguments": {"checkId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_heartbeat≈ 330 tokens

  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.

  Paramètres, retour & exemple (7)

  Paramètres

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

  Exemple d'appel

  {"name": "update_heartbeat", "arguments": {"heartbeatId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_site_settings≈ 488 tokens

  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.

  Paramètres, retour & exemple (9)

  Paramètres

  • name · string · optionnel
    Display name
  • siteId · string · requis
    The site id
  • aiTriage · string · optionnel · off | label | hold | aside
    Relvato AI triage of failed runs: label = each failure labelled needs attention / likely noise / repeat; hold = also hold back the instant alert of a confident likely-noise failure (never checkout, sign-in, uptime or security; still in the bell and digest); aside = also set that failure aside (out of the bell, digest and site health; the owner brings it back in the app); off = none (Pro and up; sends run details to Anthropic)
  • pacingMs · number|null · optionnel
    Pause between a run's requests, 0-60000 ms; null = automatic
  • jobSpacingMs · number|null · optionnel
    Pause between this site's runs, 0-900000 ms; null/0 = none
  • recoverStreak · number|null · optionnel
    Clean runs before a flaky monitor alerts again, 2-10; null = 5
  • pluginRollback · boolean · optionnel
    WordPress: roll a plugin update back when it breaks a monitor
  • challengeRetryMs · number|null · optionnel
    Wait before retrying a run a firewall challenged, 0-3600000 ms; null = 10 minutes, 0 = never
  • rumIncludeOwnChecks · boolean · optionnel
    Count Relvato's own visits in real-user Web Vitals

  Exemple d'appel

  {"name": "update_site_settings", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_visual_monitor≈ 793 tokens

  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.

  Paramètres, retour & exemple (9)

  Paramètres

  • add · array · optionnel
    Pages to start checking: each a built-in page (page) or one of your own (url)
  • remove · array · optionnel
    Keys of pages to stop checking
  • update · array · optionnel
    Pages already checked to change, by key: a new address, name or masks
  • checkId · string · requis
    The visual regression monitor's id
  • devices · array · optionnel
    Screen sizes to capture each page at (replaces the current list)
  • aiReview · boolean · optionnel
    Let AI review a change before it alerts (default on)
  • browsers · array · optionnel
    Browsers to capture each page in: chromium (Chrome, Edge), firefox, webkit (Safari); replaces the current list
  • fullPage · boolean · optionnel
    Capture the whole page (default) or only the first screen
  • thresholdPercent · number · optionnel
    How much of a page may change before it counts, 0-50 (default ~1)

  Exemple d'appel

  {"name": "update_visual_monitor", "arguments": {"checkId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_site≈ 263 tokens

  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

  Paramètres, retour & exemple (2)

  Paramètres

  • method · string · optionnel · dns | meta | gsc | bing
    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
  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "verify_site", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_vitals_beacon≈ 139 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • siteId · string · requis
    The site id

  Exemple d'appel

  {"name": "verify_vitals_beacon", "arguments": {"siteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

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