Visual Sentinel

Create an alert rule that fires when a monitor is slower than a response time or below an uptime percent.

Delete an alert rule. Its alerts stop; the built-in alerts are not affected. This cannot be undone.

Fetch one alert rule with its conditions and channels.

List alert rules: extra response-time and uptime conditions on top of the built-in alerts.

Change an alert rule's conditions, severity, channels, schedule, or turn it on or off. Send only the fields to change.

Acknowledge an alert by id (an alert-rule alert; canAcknowledge in the alert list). The acknowledgement is recorded against the account that authorised this connection.

List alerts for the authenticated organization: alert-rule alerts plus incident, server and notice history. canAcknowledge and canResolve on each entry say whether it can be acknowledged or resolved. Filter by status (UNACKNOWLEDGED/ACKNOWLEDGED/RESOLVED) or paginate.

Mark an alert as resolved, with an optional note (an alert-rule alert; canResolve in the alert list).

Add an email or WhatsApp alert channel, or get the dashboard page that finishes a channel needing a secret (Slack, Discord, Teams, PagerDuty, Opsgenie, webhook, Telegram, Prometheus, push). Your plan sets which channel types are available. New email recipients get a confirmation email.

Delete an alert channel. Monitors and rules that used it stop sending to it. This cannot be undone.

Fetch one alert channel with its settings. Secrets are hidden.

List the workspace's alert channels (email, Slack, Discord, Teams, PagerDuty, Opsgenie, webhooks, WhatsApp, Telegram, Prometheus, push). Secrets are hidden.

Send a test message through an alert channel to check it works. It reaches real people or services, and tests are limited per workspace.

Rename an alert channel, turn it on or off, choose which alerts it gets, or change its email recipients or WhatsApp numbers. Send only the fields to change. New email recipients get a confirmation email.

Resolve DNS records (A, AAAA, MX, NS, TXT, CNAME) for a domain using Visual Sentinel's public DNS lookup tool. No authentication required.

Send the Visual Sentinel team a report about a false alert, a bug or a missing feature, optionally for one monitor or incident.

Check whether Visual Sentinel itself is up. Returns the service health status. No authentication required.

Save a new limit for the problem behind an incident on its site (how slow is too slow, how long to wait before an outage alert, or how much of the page may change), then mark the incident resolved. Which incidents offer it, and the allowed range, depend on the incident. Needs monitors:write as well. The incident's alert channels and status page subscribers are told it is resolved unless notify is false.

Open an incident by hand for a monitor, for example a problem a customer reported that the checks have not caught. Subscribers of status pages that show the monitor are told about it.

Fetch a single incident with its full check history and root-cause hints.

List incidents for the authenticated organization. Filter by status (open, resolved or all), monitor id, or paginate.

Mark an incident resolved now and leave the site's settings as they are. It opens again if the problem comes back. The incident's alert channels and status page subscribers are told it is resolved unless notify is false.

Pause the checks and alerts of the monitor behind an outage incident, then mark the incident resolved. Offered for outages only. Needs monitors:write as well. The incident's alert channels and status page subscribers are told it is resolved unless notify is false.

Post a timeline update to an incident (shown on status pages) and set its status. It is sent to the incident's alert channels and status page subscribers unless notify is false. Needs an owner or admin account.

The ways an incident can be resolved: mark it resolved, change the limit for its problem, stop alerting for its check, or pause its monitor. With the suggested limit and its unit and range, what a stop would turn off, and why a way is not offered.

Turn off the check that opened an incident for its site, then mark the incident resolved. Not offered for outages or possible malware. Needs monitors:write as well. The incident's alert channels and status page subscribers are told it is resolved unless notify is false.

Change an incident: status, severity, title, description, root cause or resolution, acknowledge it (stops its repeat reminders), or turn off auto-resolve so it stays open after the site recovers. A status change is announced to its alert channels and status page subscribers unless notify is false. Send only the fields to change.

Cancel a maintenance window so alerts flow again. For a repeating window, action "skip-next" skips one occurrence and "stop-repeating" ends the repeat; with no action, or for a window that does not repeat, the whole window is cancelled.

Plan a maintenance window for some monitors. Alerts for them are held back while it runs, and status pages show the maintenance.

Delete a maintenance window and its record. This cannot be undone.

Fetch one maintenance window with its monitors and repeat settings.

List planned maintenance windows, by default from 90 days ago to about a year ahead.

Change a maintenance window's name, times, monitors or repeat. Send only the fields to change; monitorIds replaces the list.

List the regions monitors can check from, with each region code and whether it is available to this workspace.

Show whether a monitor sends a scheduled client report, to whom and how often.

Change alert settings on many monitors at once: alert timing in updates, and alert channels with channelAction (replace, add or remove) plus notificationChannelIds. Send updates, a channel action, or both.

List the alert channels a monitor sends its alerts to.

Choose exactly which alert channels a monitor sends to. The list replaces the current one; an empty list sends this monitor's alerts nowhere.

Trigger an immediate check for a monitor (in addition to its scheduled cadence). Returns the freshly-collected check result.

Create a new monitor. Provide at least name, url, and type. Returns the created monitor including its assigned id. Docs: https://visualsentinel.com/mcp#tools

Delete a monitor. It stops checking at once and leaves every status page. Deleted monitors can be restored for a limited time.

Fetch a single monitor by id, including its current status, last check, and configuration.

List monitors in the authenticated organization. Optional filters narrow by status, type, or paginate.

List recently deleted monitors that can still be restored.

Fetch uptime or response-time metrics for up to 100 monitors in a single request. Use window for a preset window (1h, 6h, 24h, 7d, 30d, 90d, 365d; default 30d), supply both from and to (ISO 8601) for a custom date range, or set all: true for the full available history. Returns a monitors object keyed by monitor id.

Mute a monitor's alerts for a while. Checks keep running and incidents are still recorded; alerts start again when the time is up or when the monitor is unmuted.

Pause a monitor: it stops checking and sends no alerts until it is resumed. Its settings and history stay.

Bring back a recently deleted monitor with its settings and history.

Resume a paused monitor: checks and alerts start again on its schedule.

Turn a muted monitor's alerts back on now.

Change where a monitor sends alerts and when: alert channels, failed checks before a down alert, delay, slow limit, slow checks before a slow alert, and repeat alerts. Only the fields sent change.

Change a monitor's name, note, address, type and API settings (such as a GraphQL query), check interval, timeout, check regions or tags, or pause and resume it. Only the fields sent change.

Choose which method this monitor's uptime check uses, and whether the check follows redirects and how many. It is a saved monitor setting the scheduled checks use. Only the fields given change.

Change a monitor's keyword checks (words the page must or must not contain), content checks on parts of the page, and the check that the page was updated recently. Only the fields sent change.

Change which response codes count as up and the text the response must contain. Only the fields sent change.

Turn a monitor's daily phone speed test on or off and set its speed limits. Only the fields sent change.

Change a monitor's scheduled client report (Business and Agency): on or off, recipient, schedule, and whether it includes charts and incidents. It does not send a report now. Only the fields sent change.

Change the saved body of a monitor's uptime check, used on each scheduled check when the check's method is POST, PUT, PATCH or QUERY. Nothing is sent now. null clears it.

Replace the request headers a monitor's check sends. Headers that carry sign-in details are entered in the dashboard; a saved one is kept.

Change how a monitor watches the SSL certificate, the domain registration and DNS records: on or off, reminder days, certificate errors, the www or bare address, and which record types to watch. Only the fields sent change.

Turn visual checks on or off and change their region and settings: change threshold, summary threshold and daily or weekly summary email, interval, viewport, areas to ignore, and video and GIF handling. Only the fields sent change. Sign-in for a page behind a login is entered in the dashboard.

Fetch the uptime percentage and time-series breakdown for a monitor. Use window for a preset window (24h, 7d, 30d, 90d, 365d; default 30d), supply both from and to (ISO 8601) for a custom date range, or set all: true for the full available history.

Add a server to watch. For AGENT servers the answer includes the dashboard page that shows the command to install the agent on the server. Your plan sets how many servers you can link.

Delete a server and stop watching it. This cannot be undone.

Fetch one server with its status and alert settings.

List servers (origins) registered in the authenticated organization.

Fetch a server's CPU, memory, disk and load over a period.

List the monitors (sites) linked to a server.

Choose exactly which monitors (sites) run on a server. The list replaces the current links.

Change a server's details, alert limits and channels, or put it in maintenance until a time. Send only the fields to change.

Run a one-shot Lighthouse lab test on a URL. Returns the performance score (0 to 100) plus Largest Contentful Paint, First Contentful Paint, Cumulative Layout Shift, Time to First Byte, Total Blocking Time and Speed Index (times in milliseconds). When the testing service is busy it answers 503 with code SPEED_TEST_SERVICE_BUSY: try again in a few minutes. No account needed. Docs: https://visualsentinel.com/mcp#tools

Inspect a TLS/SSL certificate for a hostname: issuer, subject, validity dates, SAN list, key algorithm, and certificate chain. No authentication required.

Add a group (section) to a status page. With tagRule, monitors with that tag join the group.

Delete a group from a status page. Its monitors stay on the page, outside any group.

List the groups (sections) of a status page.

Set the order of a status page's groups.

Rename a status page group or change its tag rule.

Show one or more monitors on a status page.

Turn the graph, response time or certificate display on or off for every monitor on a status page, or only the listed ones.

Remove a monitor from a status page. The monitor itself is not deleted and keeps checking.

Set the order of the monitors on a status page. The list must hold exactly the monitors on the page now.

Change how one monitor shows on a status page: its name there, graph, response time and certificate display, position, and group.

Create a status page with a name, address and visibility. Your plan sets how many you can have. Monitors and other settings are added separately.

Show one or more servers on a status page.

Remove a server from a status page. The server itself is not deleted.

Change how one server shows on a status page: its name there, whether its metrics show, and its position.

Fetch one status page with its settings, groups, monitors and servers.

List public-facing status pages owned by the authenticated organization.

Change a status page: title, address, visibility, uptime and history shown, subscriptions, order, colors and search text (Business and Agency), custom CSS and logos (Agency), and IP allowlist. Send only the fields to change. A visitor password is set in the dashboard.

Watch one more page of the same site visually, for example /pricing. Your plan sets how many extra pages each monitor can have. Docs: https://visualsentinel.com/mcp#tools

Take a fresh screenshot of one extra page now and compare it with its baseline. Refused with VISUAL_DISABLED while the monitor's visual checks are off, LIMIT_EXCEEDED when the monitor is not within the plan's visual monitor limit, and SUBPAGE_NOT_ON_PLAN for a page beyond the plan's page limit.

Delete an extra page from a visual monitor. It stops being checked.

List the extra pages (sub-pages) a visual monitor watches besides its main address, with their status and, per viewport target, the baseline and newest capture file names.

Rename an extra page, turn it on or off, reset its baseline, or accept one of its captures as the baseline.

Make a capture the new baseline, so future checks compare against it. With no screenshotId the latest capture is used. It replaces the old baseline.

Take a fresh screenshot of a monitor's page now and compare it with the baseline (in addition to the schedule). Only for a monitor with visual checks on and within the plan's visual monitor limit: otherwise it is refused with VISUAL_DISABLED or LIMIT_EXCEEDED. Captures are limited per workspace.

Show a monitor's visual check: the current baseline, the latest capture, how much it differs, and recent captures.

Quick health check for a URL: HTTP status, response time, server header, content snippet, and basic SSL state. No authentication required. Docs: https://visualsentinel.com/mcp#tools

Show how alerts that happen together are grouped and duplicates held back.

Change how alerts that happen together are grouped. Send every field: any field left out goes back to its default.

Show the workspace branding (colors, font, email footer, reply-to address, favicon) and whether white-label is on. Needs an owner or admin account.

Change the workspace branding used on reports, emails and status pages, or turn white-label on or off. Your plan sets which parts apply. Only the fields you send change. Needs an owner or admin account.

Show the workspace profile: name, logos, website, description, time zone, plan limits and usage counts. People and their details are left out.

Show the workspace defaults: server alert limits, default alert channels for new servers, the uptime target and response time limits.

Change workspace defaults. Send alertDefaults, monitoring, or both; only the fields you send change. Needs an owner or admin account.

Change the workspace name, logos, website, description or time zone. Only the fields you send change. Needs an owner or admin account.