Website monitoring API & MCP server

What Website monitoring API & MCP server does

Website monitoring API & MCP server connects an MCP-compatible agent to Relvato monitoring accounts. It exposes account and site data, monitor configuration, scan history, health summaries, performance measurements, notifications, status pages, heartbeats, and WordPress operational data.

Agents can add a site, check its ownership state, choose monitoring goals, inspect available checks, and add or dismiss recommendations. They can also read individual monitor settings and run details, including findings, warnings, metrics, screenshots, visual comparisons, and suggested fixes. Applying a suggested fix remains a user responsibility.

The server fits the 📊 Monitoring category. It is useful when an agent needs to explain why a site is failing, summarize recent monitoring activity, inspect performance trends, or help configure coverage without relying on dashboard-only browsing.

How it works

Relvato accepts read-only or full-access API keys. A newly added site may need ownership verification through the WordPress plugin, DNS TXT record, meta tag, Google Search Console, or Bing Webmaster Tools. Until verification is complete, monitors can be added but scheduled execution is deferred; public monitors can be started manually within the stated account limits.

Monitoring behavior depends on the plan. Available schedules range from weekly to every 15 minutes, and some plans support update-triggered or random additional runs. Tools report plan restrictions, active-monitor limits, setup requirements, and usage so an agent can distinguish configuration problems from failed checks.

Runs can be listed by site, monitor, or status, then retrieved in detail. Older run pages can be requested using the previous run's start time. Large metric series may be summarized, while findings remain available.

Tools and capabilities

The Website monitoring API & MCP server includes tools for:

• Listing sites, checks, runs, notifications, activity records, status pages, heartbeats, and settings.
• Adding sites, verifying ownership, calibrating WordPress or WooCommerce stores, and checking the real-user Web Vitals beacon.
• Starting monitoring by goals such as flows, security, search, accessibility, speed, domain, or AI-related checks.
• Adding, updating, pausing, resuming, or removing monitor behavior, including visual regression settings and monitor-specific configuration.
• Reading site overviews, health trends, performance data, monitor details, run findings, fix context, safe updates, quarantine state, and WordPress activity.
• Reviewing alert channels, public status pages, client reports, heartbeat schedules, and account usage.

Visual monitors can cover built-in or custom pages, masks, devices, browsers, full-page captures, thresholds, and AI review. Other settings cover flows, checkout, accessibility, uptime, broken links, errors, structured content, email authentication, web vitals, and related checks where supported by the monitor.

Setup and configuration

Create or use a Relvato API key and provide it to the MCP server using the deployment method documented by Relvato.

After connecting, list the account's sites and inspect setup state before adding checks. For WordPress sites, connect the plugin when required. For non-WordPress sites, use the available domain-verification method. Ownership, plan level, and credential scope determine which operations can run.

Limitations and notes

Dashboard-only changes include several alert, connection, firewall, browser identity, GitHub, and reporting settings. The tools expose sensitive values selectively: webhook URLs and secrets are not returned, and heartbeat ping URLs are available only to full-access connections. Pausing a monitoring group can stop active monitors, so confirm the user's intent first. Scheduled runs, alerts, updates, quarantine, and some monitor types require ownership proof or a suitable paid plan.