← Registry

DevOps

watchfor.io

Provides monitoring snapshots, incident statistics, and scheduled reports for an organization's monitors.

WebMCP3 endpoints44 known toolsFirst detected September 2, 2026Last detected September 6, 2026

ENDPOINT 1

https://watchfor.io/api/mcp

No auth detected

MCP server metadata

Name
WatchFor
Version
1.0.0
Capabilities
toolsresourcesprompts
Server instructions

WatchFor uptime & infrastructure monitoring. Start with get_summary for the current state of the organization's monitors and incidents. Before creating monitors or alert rules, call get_monitor_types — it lists every monitor type's target format, config fields and the EXACT alert metric strings. All mutating tools require an API key with the write scope; validation errors state the allowed values, so correct the arguments and retry.

Known tools 40

get_summary

One-call organization snapshot: monitor status counts (up/down/paused/unknown + health score), active incident counts and open maintenance windows.

Inferred read-only
get_incident_stats

Aggregate incident statistics over a period: totals by severity, MTTR (mean time to resolve), MTBF and the five most unstable monitors.

Inferred read-only
get_report

Org report for a period, always compared with the previous equal-length period: uptime, incidents, MTTR/MTBF, downtime, response-time trend, per-monitor rows (worst first), type-aware sections (SSL/domain expiry, Core Web Vitals, heartbeat check-ins, DNS blocklists, MCP tool drift) and plain-language insights.

Inferred read-only
get_report_schedules

The organization's two scheduled report-email cadences (weekly + monthly): enabled state, recipients (max 5) and any recipients who unsubscribed themselves.

Potential side effects
set_report_schedule

Enable/disable the weekly or monthly report email and/or replace its recipient list (up to 5 addresses).

Potential side effects
get_plan

Current subscription plan with limits (-1 = unlimited, 0 = feature off) and live usage counts.

Inferred read-only
list_monitors

List monitors (cursor-paginated, slim items: id/name/type/target/status/tags — use get_monitor for full detail).

Inferred read-only
get_monitor

Get one monitor by id — includes config and available_metrics (the alert metrics valid for its type).

Inferred read-only
get_monitor_types

Discovery catalog of all 25 monitor types: target format, default alert rules, per-type alert metrics (exact `metric` strings, operators, value types) and config fields.

Inferred read-only
create_monitor

Create a monitor (write scope).

Potential side effects
update_monitor

Update monitor fields (write scope).

Potential side effects
set_monitor_paused

Pause or resume a monitor (write scope).

Potential side effects
delete_monitor

Permanently delete a monitor (write scope).

Potential side effects
run_check_now

Dispatch an immediate on-demand check for a monitor (write scope, plan-limited per hour).

Potential side effects
get_monitor_uptime

Uptime percentage and check totals for a monitor over a period (scheduled maintenance excluded).

Inferred read-only
get_monitor_checks

Recent check results for a monitor (status, latency, per-location performance).

Inferred read-only
list_locations

Probe locations available for monitors — use these ids in create_monitor's locations array.

Inferred read-only
list_alert_rules

List a monitor's alert rules (system defaults + custom).

Inferred read-only
create_alert_rule

Create an alert rule on a monitor (write scope).

Potential side effects
update_alert_rule

Update an alert rule (write scope) — fix a noisy threshold, change severity, or enable/disable.

Potential side effects
delete_alert_rule

Delete a custom alert rule (write scope).

Potential side effects
list_contacts

Alert recipients (people) with their group memberships — answers 'who gets notified?'.

Inferred read-only
get_contact

One contact's detail: name, email, phone, group memberships.

Potential side effects
create_contact

Create an alert recipient (write scope).

Potential side effects
update_contact

Update a contact (write scope).

Potential side effects
delete_contact

Delete a contact (write scope) — removes them from all notification groups.

Potential side effects
list_contact_groups

Notification groups (contact groups) — where alerts are delivered.

Inferred read-only
get_contact_group

One notification group's detail INCLUDING its member list (who exactly gets paged).

Inferred read-only
create_contact_group

Create a notification group (write scope), optionally with initial members (contact ids from list_contacts).

Potential side effects
update_contact_group

Update a notification group (write scope).

Potential side effects
delete_contact_group

Delete a notification group (write scope).

Potential side effects
list_incidents

List incidents newest first (cursor-paginated).

Inferred read-only
get_incident

Full detail of one incident: what fired, trigger values, confirmations, timeline.

Inferred read-only
acknowledge_incident

Acknowledge a firing incident (write scope) — pauses repeat notifications while someone investigates.

Potential side effects
resolve_incident

Manually resolve an incident (write scope).

Potential side effects
list_notifications

Alerting delivery history — every notification attempt with channel, delivery status (sent/failed/silenced), severity, incident and monitor.

Inferred read-only
list_activity

The organization's audit trail — who changed what and when (monitors, alert rules, contacts, maintenance, channels; dashboard AND API actions).

Inferred read-only
list_maintenance_windows

List scheduled maintenance windows, most recent first.

Inferred read-only
create_maintenance_window

Schedule a maintenance window (write scope): alerts are suppressed and downtime excluded from uptime for the covered monitors during the window.

Potential side effects
delete_maintenance_window

Cancel a maintenance window (write scope) — removes future occurrences and lifts any active silences.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.watchfor]
url = "https://watchfor.io/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "watchfor": {
      "type": "http",
      "url": "https://watchfor.io/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: watchfor
Remote MCP URL: https://watchfor.io/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "watchfor": {
      "url": "https://watchfor.io/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "watchfor": {
      "type": "http",
      "url": "https://watchfor.io/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "watchfor",
  "transport": "streamable-http",
  "url": "https://watchfor.io/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://watchfor.io/docs/api/mcp

No auth detected

MCP server metadata

Name
WatchFor Docs
Version
1.0.0
Capabilities
tools
Server instructions

WatchFor documentation, over MCP. Use list_docs to see every page, search_docs to find pages by keyword, and read_doc to pull a page's full markdown. This server is read-only and needs no authentication. To ACT on an account (create monitors, read incidents, …) use the product MCP server at /api/mcp instead.

Known tools 3

list_docs

List WatchFor documentation pages with path, title and description.

Inferred read-only
search_docs

Search the documentation by keyword; returns matching pages (path, title, description) ranked by relevance.

Inferred read-only
read_doc

Return the full markdown of one documentation page.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.watchfor-docs]
url = "https://watchfor.io/docs/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "watchfor-docs": {
      "type": "http",
      "url": "https://watchfor.io/docs/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: watchfor-docs
Remote MCP URL: https://watchfor.io/docs/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "watchfor-docs": {
      "url": "https://watchfor.io/docs/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "watchfor-docs": {
      "type": "http",
      "url": "https://watchfor.io/docs/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "watchfor-docs",
  "transport": "streamable-http",
  "url": "https://watchfor.io/docs/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 3

https://watchfor.io

No auth detected

MCP server metadata

Name
WebMCP
Capabilities
declarative

Known tools 1

run_free_website_audit

Run a free Smart Website Audit (uptime, SSL, DNS, security headers, performance) on the entered URL — no signup required.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.webmcp]
url = "https://watchfor.io"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "webmcp": {
      "type": "http",
      "url": "https://watchfor.io"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: webmcp
Remote MCP URL: https://watchfor.io

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "webmcp": {
      "url": "https://watchfor.io"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "webmcp": {
      "type": "http",
      "url": "https://watchfor.io"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "webmcp",
  "transport": "streamable-http",
  "url": "https://watchfor.io"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.