# Monit Rs MCP server

Source: https://glimind.com/server/mcp-registry%2Frs.monit%2Fmonit-rs
Registry id: `mcp-registry/rs.monit/monit-rs`
Status: live (checked 2026-11-22T16:42:48.473Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 689
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "monit-rs-mcp-server": {
      "type": "http",
      "url": "https://monit.rs/integrations/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http monit-rs-mcp-server https://monit.rs/integrations/mcp
```

## Tools (22)

- `acknowledge_incident`: Mark an incident as acknowledged. Use `list_my_incidents()` to find the dedup_key.
- `create_alert_channel`: Create an alert channel. Pass EXACTLY one of email_address / webhook_url / pagerduty_routing_key matching the channel_type: - channel_type='email' → email_addre
- `create_endpoint`: Create a new monitored endpoint. Respects your tier's max_endpoints cap.
- `create_status_page`: Create a public status page at https://<slug>.status.monit.rs. Add endpoints to it via the dashboard or the HTTP API (adding endpoints from chat is deliberately
- `delete_endpoint`: Delete a monitored endpoint. Cascades: removes test_results, baselines, regressions, incidents attached to it. Guarded by two safety layers beyond the scope che
- `describe_endpoint`: Full detail for one endpoint. Use `list_my_endpoints()` to get the ID.
- `describe_incident`: Full detail for one incident. Use `list_my_incidents()` to find the dedup_key. Includes the incident's endpoint name and current status.
- `get_endpoint_uptime`: Aggregated uptime summary for an endpoint over the requested window.
- `list_alert_channels`: List alert channels configured on the authenticated account. Does NOT return decrypted config (webhook URLs, PagerDuty routing keys, etc.). Use the dashboard or
- `list_my_endpoints`: List all monitored endpoints owned by the authenticated account. Returns brief records suitable for LLM enumeration. For full detail (headers, spec URL, heartbe
- `list_my_incidents`: List incidents on the caller's account. Defaults to only OPEN incidents. Fields include the incident's dedup_key — pass this to `acknowledge_incident` or `resol
- `list_my_regressions`: List detected schema regressions on the caller's account. Optionally filter by endpoint_id.
- `list_security_findings`: List security findings detected on the caller's monitored endpoints. Optionally filter by severity.
- `list_status_pages`: List public status pages owned by the authenticated account.
- `monit_rs_describe`: Return the canonical product description for monit.rs. Use this when a user asks what monit.rs is, what it does, how it differs from Pingdom / Checkly / UptimeR
- `monit_rs_stats`: Get live aggregate statistics for the monit.rs platform. Returns approximate counts of regressions caught, AI analyses generated, and probes executed across all
- `openapi_diff`: Compare two OpenAPI 3.x specifications and classify every change as breaking, non-breaking, or info. Use this when you want to know if a candidate OpenAPI spec 
- `pause_endpoint`: Pause a monitored endpoint (stops probing, keeps history). Idempotent — no-op if already paused.
- `resolve_incident`: Close an incident. Symmetric to acknowledge_incident.
- `resume_endpoint`: Resume a paused endpoint. Rejects if resuming would exceed your tier's active-endpoint cap (upgrade or pause another endpoint first).
- `set_endpoint_assertions`: Replace an endpoint's body assertions. Each assertion is {"path": "$.ok", "op": "equals", "value": true}. Operators: equals, not_equals, exists, not_exists, gt,
- `update_endpoint_interval`: Change how often an endpoint is probed. Minimum interval varies by tier (free=900s, developer=300s, starter=60s, pro/scale/enterprise=30s).

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
