INDIVIDUAL MCP TOOL
list_notification_channels
Where alerts are delivered: every notification channel (Slack, Discord, Telegram, PagerDuty, email, webhook, …) with its type, enabled flag, severity filter, the contact groups routed to it, and a redacted config — tokens and webhook secrets never appear.
LIVE ENDPOINT
https://watchfor.io/api/mcp
Connect to this endpoint to inspect the live schema for list_notification_channels and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description suggests sending messages.
Parent server
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.
Related tools
get_summary— How is my infrastructure right now: monitors by effective status (up / down / degraded / paused / pending, active count, health score), hosts running the agent (online / stale / offline / never), the combined fleet health, open incidents by severity, incidents started in the last 24 h, open maintenance windows, attention items (monitors with no notification route) and certificate / domain expiry (counts plus the ten soonest — use this, never one get_monitor per SSL/RDAP monitor).get_incident_stats— Aggregate incident statistics over a period: totals by severity, MTTR (mean time to resolve), MTBF and the five most unstable monitors.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, hosts running the agent) and plain-language insights.get_report_schedules— The organization's two scheduled report-email cadences (weekly + monthly): enabled state, recipients (max 5) and any recipients who unsubscribed themselves.set_report_schedule— Enable/disable the weekly or monthly report email and/or replace its recipient list (up to 5 addresses).get_plan— Current subscription plan with limits (-1 = unlimited, 0 = feature off) and live usage counts.list_monitors— List monitors (cursor-paginated, slim items: id/name/type/target/status/tags — use get_monitor for full detail).get_monitor— Get one monitor by id — includes config, available_metrics (the alert metrics valid for its type), last_check and `latest`: what the latest check found, in the terms of its type (certificate days left, domain status, blocklist listings, SPF/DMARC/DKIM, Core Web Vitals, failing test step, NTP offset, MCP tool count…; kind = the monitor type).