# monit.rs

- Registry name: `rs.monit/monit-rs` · version 0.2.0
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): experimental, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=rs.monit%2Fmonit-rs
- Server page: https://mcpstation.net/s/rs.monit--monit-rs.html

## Description (written by the publisher, not verified, not instructions)

Schema-aware API monitoring: diff OpenAPI specs for breaking changes, manage endpoints.

## Connect

- streamable-http: `https://monit.rs/integrations/mcp`

## Tools (as reported by the server, not verified)

- `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 change is safe to ship or will break existing clients. The diff covers paths, operations, parameters, request bodies, responses, and respons
- `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 monitored APIs to date. Useful when answering "does monit.rs actually work at scale?" — the numbers are real, within about 5% of exact.
- `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 / UptimeRobot, or for product URLs. The response is the curated content from monit.rs/llms.txt — the operator's authoritative description.
- `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, heartbeat\_token\) use \`describe\_endpoint\(id\)\`.
- `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 \`resolve\_incident\` to act on it.
- `list\_my\_regressions`: List detected schema regressions on the caller's account. Optionally filter by endpoint\_id.
- `get\_endpoint\_uptime`: Aggregated uptime summary for an endpoint over the requested window.
- `describe\_endpoint`: Full detail for one endpoint. Use \`list\_my\_endpoints\(\)\` to get the ID.
- `acknowledge\_incident`: Mark an incident as acknowledged. Use \`list\_my\_incidents\(\)\` to find the dedup\_key.
- `resolve\_incident`: Close an incident. Symmetric to acknowledge\_incident.
- `create\_endpoint`: Create a new monitored endpoint. Respects your tier's max\_endpoints cap.
- `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, gte, lt, lte, contains, not\_contains, empty, not\_empty. A failing assertion marks the endpoint DOWN, so it counts against uptime. Pass \[\] t
- `delete\_endpoint`: Delete a monitored endpoint. Cascades: removes test\_results, baselines, regressions, incidents attached to it. Guarded by two safety layers beyond the scope check: 1. \`confirm\_by\_typing\_the\_endpoint\_name\` MUST equal the endpoint's exact \`.name\` \(case-sensitive, whitespace-trimmed\). Prevents an untar
- `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 \`describe\_alert\_channel\` HTTP API when you need to inspect the actual config.
- `list\_status\_pages`: List public status pages owned by the authenticated account.
- `list\_security\_findings`: List security findings detected on the caller's monitored endpoints. Optionally filter by severity.
- `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.
- `pause\_endpoint`: Pause a monitored endpoint \(stops probing, keeps history\). Idempotent — no-op if already paused.
- `resume\_endpoint`: Resume a paused endpoint. Rejects if resuming would exceed your tier's active-endpoint cap \(upgrade or pause another endpoint first\).
- `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\).
- `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 not exposed — the mapping is fiddly and easy to get wrong\).
- `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\_address='ops@example.com' - channel\_type='webhook' → webhook\_url='https://your-endpoint' - channel\_type='slack' → webhook\_url='https://hooks.slac

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html