Agent MCP Directory

Relvato: MCP server, CLI and agent surfaces

Yes: Relvato runs a public MCP server at app.relvato.com that listed 58 tools to a client with no credentials on 4 November 2026. Examples: list_sites, add_site, verify_site. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool.

Fact sheet

CompanyRelvato
Domainrelvato.com
CategoryInfrastructure (assigned by this directory from the registry description)
MCP serverVerified (No authentication)
Ora scorenone: Ora returned no cached score for relvato.com when asked on 5 November 2026
Company found throughthe GitHub MCP Registry; the official MCP Registry
Last verified4 November 2026

MCP server

Endpointhttps://app.relvato.com/api/mcp
How it was foundlisted in the GitHub MCP Registry; the official MCP Registry
Transportstreamable-http
HTTP status200
Protocol version2025-06-18
Serverrelvato 3.5.1
Capabilitiestools
Tools58
Resources0
Prompts0
Connected4 November 2026, 20:04 UTC
Handshake time642 ms over 1 attempt

Tools listed

58 tools; the first 40 names are recorded

  • list_sites
  • add_site
  • verify_site
  • start_monitoring_for_goals
  • list_checks
  • add_checks
  • dismiss_recommendation
  • calibrate_site
  • verify_vitals_beacon
  • site_overview
  • get_site_health
  • get_performance
  • get_check
  • list_runs
  • get_run
  • get_fix_prompt
  • get_updates
  • get_safe_update
  • get_quarantine
  • get_activity_log
  • get_notifications
  • get_site_settings
  • get_alert_settings
  • get_status_pages
  • list_heartbeats
  • update_check
  • pause_monitor_group
  • resume_monitor_group
  • update_visual_monitor
  • update_check_settings
  • add_custom_check
  • edit_custom_check
  • reauthor_custom_check
  • approve_custom_check
  • update_site_settings
  • update_alert_settings
  • add_heartbeat
  • update_heartbeat
  • trigger_scan
  • cancel_queued_runs

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:59:09Z https://app.relvato.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1066 ms
  • 20:04:14Z https://app.relvato.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 642 ms

Authentication

Auth typeNo authentication

The sign-in route, step by step

  1. Send the handshake to https://app.relvato.com/api/mcp over streamable-http. Servers on the 2026-07-28 revision answer server/discover; older servers answer initialize.
  2. Send tools/list, then resources/list and prompts/list if the capabilities name them.
  3. Send no token. The connector sent none and the server answered, so any MCP client can read this list.
  4. Calling a tool is a separate step this directory never takes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for Relvato. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot checked: the home page was not read by the shared crawl.
MCP discovery fileNot checked: the domain is not in the shared crawl for this edition.
A2A agent cardNot checked: the domain is not in the shared crawl for this edition.
A2A agent card (older path)Not checked: the domain is not in the shared crawl for this edition.
agents.jsonNot checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadataNot checked: the domain is not in the shared crawl for this edition.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: com.relvato/relvato
GitHub MCP RegistryYes
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.