Relvato

[Relvato]

Relvato MCP server

Website monitoring your AI agent can run: add a site, pick its checks, run them and explain what broke.
Developer docs · Official MCP Registry · relvato.com

Relvato monitors websites in a real browser. It checks sign-ups, logins, checkout, payments, page speed, search visibility and security, and re-checks them every time the site changes. It works on any website and goes deepest on WordPress & WooCommerce.

This is Relvato's hosted Model Context Protocol server. There's nothing to install or run: point your MCP client at the URL and authenticate with a Relvato API key. This repository holds the connection details and the registry entry (server.json). The server itself runs at Relvato.

Get an API key

1. Sign up (there's a free plan) or sign in.
2. Open API access from the account menu, or go to app.relvato.com/api-access.
3. Create a key:
   • Full access lets the agent add sites and checks, change schedules and run scans.
   • Read-only lets it read sites, runs, health overviews, fix briefs and alert settings. With a read-only key the client only sees the read tools.

A key is shown once. Keep it out of files you commit.

Connect

Claude Code

claude mcp add --transport http relvato https://app.relvato.com/api/mcp --header "Authorization: Bearer rlv_your_key"

Cursor

In ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{  "mcpServers": {    "relvato": {      "url": "https://app.relvato.com/api/mcp",      "headers": {        "Authorization": "Bearer rlv_your_key"      }    }  }}

VS Code

In .vscode/mcp.json. VS Code asks for the key once and stores it securely, so it never sits in the file:

{  "inputs": [    { "type": "promptString", "id": "relvato-key", "description": "Relvato API key (rlv_…)", "password": true }  ],  "servers": {    "relvato": {      "type": "http",      "url": "https://app.relvato.com/api/mcp",      "headers": {        "Authorization": "Bearer ${input:relvato-key}"      }    }  }}

Cline

In cline_mcp_settings.json (MCP Servers → Configure):

{  "mcpServers": {    "relvato": {      "type": "streamableHttp",      "url": "https://app.relvato.com/api/mcp",      "headers": {        "Authorization": "Bearer rlv_your_key"      }    }  }}

Agents that set servers up themselves can follow llms-install.md.

Any other client

Add a remote HTTP (streamable HTTP) server with the endpoint above and an Authorization: Bearer rlv_… header. In the common mcp.json format:

{  "mcpServers": {    "relvato": {      "type": "http",      "url": "https://app.relvato.com/api/mcp",      "headers": {        "Authorization": "Bearer rlv_your_key"      }    }  }}

Relvato uses API keys, not OAuth, so a client needs to be able to send a custom header. Clients that accept only a bare URL can list the tools but can't call them.

Tools

initialize and tools/list answer without a key, so directories and clients can show what the server offers. Every tool call needs one.

Things to ask

• "Set up monitoring for example.com and tell me what I need to do to connect it."
• "Why did checkout fail on my shop last night, and how do I fix it?"
• "Who gets alerted when a Security check fails, and on which channels?"
• "Run the checks on my site now and tell me if anything broke."

What an agent can't do

These stay in the Relvato dashboard, with a person looking:

• Skip ownership. A new site runs no checks until its WordPress plugin is connected or its domain is verified.
• Accept changes. Accepting new visual baselines and ignoring warnings are done in the dashboard.
• Apply fixes. No fixes are applied to your site.
• Touch secrets. Connect tokens, signing secrets and webhook URLs are never exposed.
• Go past your plan. Plan limits apply exactly as in the dashboard.

Limits

Requests are rate-limited per account, per minute, counted across the REST API and MCP together:

Runs started with trigger_scan count toward the same monthly run quota as scheduled checks. See pricing.

Also available

• REST API. The same data at https://app.relvato.com/api/v1, using the same keys. See the developer docs.
• Webhooks. A signed JSON event for every alert (Pro and up).

Support

• Questions and bug reports: relvato.com/contact, or open an issue here.
• Service status: relvato.com/status.
• Security issues: please use the contact page, not a public issue.

This repository contains documentation and configuration only. The Relvato service is proprietary and covered by its terms. The contents of this repository are MIT-licensed (see LICENSE), so copy the config snippets freely.