# monit.rs

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

- name: rs.monit/monit-rs
- version: 0.2.0
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/rs.monit%2Fmonit-rs
- tools: https://api.protogrid.dev/v1/servers/rs.monit%2Fmonit-rs/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 98
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-95% +updated-16d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: openapi_diff (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_my_incidents (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); acknowledge_incident (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 2,355 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 1 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 22, about 2,355 tokens to load them all
- tool set hash: f87c22f845431d7104e74216b0d6939c
- tools last changed: 2026-10-15T16:49:27.026Z
- badge: [![protogrid quality](https://protogrid.dev/badge/rs.monit/monit-rs.svg)](https://protogrid.dev/servers/rs.monit/monit-rs)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-15 `set_endpoint_assertions` added
  - 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 [] to clear.

Full history: https://api.protogrid.dev/v1/servers/rs.monit%2Fmonit-rs/changes

## Remotes

- https://monit.rs/integrations/mcp (streamable-http, auth none, reachable true, uptime30d 0.9508197)

## Packages

_none_

## 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_address='ops@example.com'
      - channel_type='webhook'   → webhook_url='https://your-endpoint'
      - channel_type='slack'     → webhook_url='https://hooks.slack.com/...'
      - channel_type='pagerduty' → pagerduty_routing_key='<Events v2 key>'
    
- `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 not exposed — the mapping is
    fiddly and easy to get wrong).
- `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 untargeted "delete stuff" LLM-injection: the model has to
       first `describe_endpoint(id)` to learn the name, then include
       it verbatim.

    2. Per-user destructive-op cap of 5/day. Legitimate bulk deletes
       should use the HTTP API or dashboard.
    
- `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 `describe_alert_channel` HTTP API when you
    need to inspect the actual config.
    
- `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.
- `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 / UptimeRobot, or for product URLs.
    The response is the curated content from monit.rs/llms.txt — the
    operator's authoritative description.
    
- `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.
    
- `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
    response-body schema fields (added/removed/retyped, required toggle).

    Both arguments are the OpenAPI spec as a JSON or YAML string.
    Returns {summary: {breaking, non_breaking, info}, changes: [...]}.
    
- `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, gte, lt, lte,
    contains, not_contains, empty, not_empty. A failing assertion marks the
    endpoint DOWN, so it counts against uptime. Pass [] to clear.
    
- `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).