Reads monitoring data, adds websites and checks, and runs scans through REST API and MCP access.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
Clients with native remote MCP support can connect directly to this URL instead of the install method above.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Website monitoring API & MCP server.
list_sitesList the websites in this Relvato account, with whether each is ready to run monitors.
add_siteStart 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 domain (the only option for non-WordPress sites). 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
verify_siteCheck 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
start_monitoring_for_goalsThe 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.
list_checksThe 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.
add_checksAdd 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). New monitors run on their default triggers: a weekly (some daily) schedule, plus a re-run when the site changes (WordPress plugin updates, or pushes via the GitHub App).
Website monitoring API & MCP server gives AI agents access to Relvato's website monitoring functionality. The provided capabilities cover three broad tasks: reading monitoring data, adding websites, and adding checks. Agents can also request scans, allowing monitoring activity to be initiated through the available API or MCP interface.
The service is relevant when an agent needs to work with website monitoring information as part of an automated or conversational workflow. For example, an agent can use the read capability to inspect existing monitoring data, then use the mutation capabilities to add a website or check. The supplied description does not specify the exact monitoring fields, check types, scan parameters, or response formats.
Relvato exposes the functionality through both a REST API and an MCP server. An AI agent connects using an API key, and the key's permission level determines whether it can only read data or also perform changes. Read-only keys are intended for inspection. Full-access keys enable the write and scan operations described for the service.
The MCP interface is the relevant option when the consuming application supports Model Context Protocol tools. The REST API is available for clients or automation that work directly with HTTP APIs. No transport details, endpoint paths, request examples, or MCP tool names are provided in the available material.
Configuration requires an API key. Choose a read-only key when the agent only needs monitoring data, or use a full-access key when it must add websites, add checks, or run scans. The source material does not provide installation commands, environment-variable names, authentication headers, hosted-versus-local deployment details, or client-specific configuration files.
Before granting full access, match the key permission to the agent's intended role. An agent that only reports on monitoring status does not need the broader permission described for modification and scan operations.
The documented capabilities include:
Website monitoring API & MCP server is documented here only at a capability level. The available information does not identify supported monitoring providers, website-check options, scan behavior, rate limits, error responses, retention rules, or result schemas. It also does not name compatible MCP clients or provide a license.
The Relvato developer source should be consulted for the exact API contract and setup procedure before implementation. In particular, developers should verify how keys are supplied, which operations require full access, and how monitoring data and scan results are represented.
Factual signals from GitHub, npm, and our automated checks โ not a rating.
No reviews yet โ be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/website-monitoring-api-mcp-server)<a href="https://allmcps.com/mcp/website-monitoring-api-mcp-server"><img src="https://allmcps.com/api/badge/website-monitoring-api-mcp-server?style=directory" alt="Website monitoring API & MCP server on AllMCPs" /></a>