Relvato
REMOTE · APP.RELVATO.COM
Website monitoring: add sites, configure and run monitors, read health, review results, apply fixes.
Available components
Last scanned (1 hour ago)
Scores higher than 96% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security100
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7853 tokens (~135/item across 58 items; 58 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 59 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 3.2.0 → 3.3.0 functional
- New tool “bring_back_run” functional
- “update_site_settings” added an optional parameter “aiTriage” cosmetic
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “apply_fix” rewrote its description, which is the text the model reads security
- Tool “start_safe_update” rewrote its description, which is the text the model reads security
- 13 Oct 26 +1
- DNSSEC: fail → pass ▲ security
- 12 Oct 26 +1
- Tool “apply_fix” rewrote its description, which is the text the model reads security
- Tool “start_quarantine” rewrote its description, which is the text the model reads security
- Tool “start_safe_update” rewrote its description, which is the text the model reads security
- 10 Oct 26 +1
- Tool “flag_visual_change_as_problem” rewrote its description, which is the text the model reads security
- Tool “get_run” rewrote its description, which is the text the model reads security
- Tool “get_site_health” rewrote its description, which is the text the model reads security
- 7 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “start_monitoring_for_goals” rewrote its description, which is the text the model reads security
- Tool “update_check_settings” rewrote its description, which is the text the model reads security
- Tool “verify_site” rewrote its description, which is the text the model reads security
- Schema quality: 6481 → 7402 ▼ functional
- Server version: 3.1.0 → 3.2.0 functional
- New tool “add_heartbeat” functional
- New tool “list_heartbeats” functional
- New tool “update_heartbeat” functional
- “update_check_settings” added an optional parameter “uptime” cosmetic
- “pause_monitor_group” reworded the description of “group” cosmetic
- “trigger_scan” reworded the description of “group” cosmetic
- “verify_site” reworded the description of “method” cosmetic
- 5 Oct 26 0
- Tool “update_check_settings” rewrote its description, which is the text the model reads security
- “update_check_settings” added an optional parameter “accessibilityPages” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://app.relvato.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.relvato.com | CN=YR2,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 5d5412c688d9b619b56f7b90441ce51daee |
| SANs: app.relvato.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of app.relvato.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| relvato.com. | present | 2371 | 13 | Verified |
| app.relvato.com. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://app.relvato.com/.well-known/oauth-protected-resource/api/mcp", scope="relvato:read relvato:write user:org:read"
Bearer resource_metadata="https://app.relvato.com/.well-known/oauth-protected-resource/api/mcp", scope="relvato:read relvato:write user:org:read"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | frame-ancestors 'none'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), usb=() |
Protected resource metadata
| Document | https://app.relvato.com/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://app.relvato.com/api/mcp |
| Authorisation server | https://clerk.relvato.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.relvato.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.relvato.com/api/mcp | HTTPS enforced | 308 | https://app.relvato.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
update_alert_settings Change alert timing and severity ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| digestTime | string | – | HH:MM (24h) for the daily / weekly digest |
| digestWeekday | number | – | Weekly digest day, 0 = Sunday … 6 = Saturday |
| everyRun | boolean | – | Email every run, not only problems |
| frequency | array | – | – |
| minSeverity | string | – | – |
| timezone | string | – | IANA time zone for the digest, e.g. Europe/Berlin |
No output schema declared.
No examples provided.
update_check Update a monitor ~279
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.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | Daily/weekly run time, HH:MM (24h) |
| checkId | string | yes | The monitor's id (from site_overview or add_checks) |
| dow | number | – | Weekly only: weekday, 0 = Sunday … 6 = Saturday |
| enabled | boolean | – | Turn the monitor on or off |
| events | array | – | 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 | – | Random extra runs (times per days), with an off or weekly schedule; null turns them off |
| schedule | string | – | Recurring schedule |
| tz | string | – | IANA timezone for `at`, e.g. Europe/Berlin |
No output schema declared.
No examples provided.
update_check_settings Change a monitor's settings ~480
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accessibilityPages | array | – | 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 |
| aiOutput | object | – | The site's own AI feature: its endpoint (full URL on the site), a fixed prompt, and what the answer must (not) contain |
| brokenLinks | object | – | Extra pages to crawl, address fragments to skip, and whether external links are checked too |
| browseUrl | string | – | Storefront: the shop page (blank = the calibrated one) |
| checkId | string | yes | The monitor's id |
| checkout | object | – | Checkout monitors |
| devices | array | – | Flow and page monitors |
| dkimSelectors | array | – | Email authentication: your mail provider's DKIM selectors (up to 10) |
| errorScan | object | – | Extra pages to scan (full URLs on the site) and error texts to ignore |
| productUrl | string | – | Prices: a sample product |
| shopUrl | string | – | Prices: the shop page |
| structurePages | array | – | Structure drift: pages to fingerprint |
| uptime | object | – | 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) |
| webVitalsDevices | array | – | Core Web Vitals: devices to measure |
No output schema declared.
No examples provided.
update_heartbeat Update a heartbeat ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cron | string | – | A cron expression to use instead of the period ("" switches back to the period) |
| graceSec | number | – | Grace time in seconds (60 to 604800) |
| heartbeatId | string | yes | The heartbeat's id (from list_heartbeats or add_heartbeat) |
| name | string | – | New name |
| paused | boolean | – | true pauses it, false resumes it |
| periodSec | number | – | How often the job runs, in seconds (60 to 2678400); switches a cron schedule back to a period |
| tz | string | – | The cron expression's IANA time zone |
No output schema declared.
No examples provided.
update_site_settings Change a site's settings ~338
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.
| Name | Type | Req | Description |
|---|---|---|---|
| aiTriage | string | – | 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, s… |
| challengeRetryMs | number|null | – | Wait before retrying a run a firewall challenged, 0-3600000 ms; null = 10 minutes, 0 = never |
| jobSpacingMs | number|null | – | Pause between this site's runs, 0-900000 ms; null/0 = none |
| name | string | – | Display name |
| pacingMs | number|null | – | Pause between a run's requests, 0-60000 ms; null = automatic |
| pluginRollback | boolean | – | WordPress: roll a plugin update back when it breaks a monitor |
| recoverStreak | number|null | – | Clean runs before a flaky monitor alerts again, 2-10; null = 5 |
| rumIncludeOwnChecks | boolean | – | Count Relvato's own visits in real-user Web Vitals |
| siteId | string | yes | The site id |
No output schema declared.
No examples provided.
update_visual_monitor Change the visual monitor's pages ~276
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.
| Name | Type | Req | Description |
|---|---|---|---|
| add | array | – | – |
| aiReview | boolean | – | Let AI review a change before it alerts (default on) |
| browsers | array | – | – |
| checkId | string | yes | The visual regression monitor's id |
| devices | array | – | – |
| fullPage | boolean | – | Capture the whole page (default) or only the first screen |
| remove | array | – | Keys of pages to stop checking |
| thresholdPercent | number | – | How much of a page may change before it counts, 0-50 (default ~1) |
| update | array | – | – |
No output schema declared.
No examples provided.
verify_site Verify site setup ~147
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
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | 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)… |
| siteId | string | yes | The site id |
No output schema declared.
No examples provided.
verify_vitals_beacon Verify the real-user beacon ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| siteId | string | yes | The site id |
No output schema declared.
No examples provided.
How do I install the Relvato MCP server?
Relvato is a hosted endpoint at https://app.relvato.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.relvato.com
claude mcp add --transport http com-relvato-relvato 'https://app.relvato.com/api/mcp'
What is the Relvato MCP server?
Relvato is an MCP server listed in the public MCP registry as com.relvato/relvato. Website monitoring: add sites, configure and run monitors, read health, review results, apply fixes. This page covers its hosted endpoint (https://app.relvato.com/api/mcp).
Is the Relvato MCP server safe to use?
Relvato scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Relvato MCP server expose?
Relvato exposes 58 tools: list_sites, add_site, verify_site, start_monitoring_for_goals, list_checks, and 53 more. Their descriptions and schemas cost roughly 7,204 tokens of context every time the server is loaded.
Does the Relvato MCP server require authentication?
Yes. Relvato asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Relvato MCP server still maintained?
Relvato is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.