Skip to content

monit.rs

by monit.rs · remote · no sign-in to list tools · v0.2.0 · published by rs.monit

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

Deletes · 1Changes · 9
CompareRegistry entry

22 tools: 1 can delete or cancel things, 9 change things and 12 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

22 tools

Deletes or cancels 1Claude Code: deny
  • delete_endpointDelete a monitored endpoint.No findings

    Why it is in this group

    • The name "delete_endpoint" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    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.
Changes things 9Claude Code: ask
  • acknowledge_incidentMark an incident as acknowledged.No findings

    Why it is in this group

    • The description's first verb is "mark": a word for a change.
    Description, as the server wrote it
    Mark an incident as acknowledged. Use `list_my_incidents()` to find the dedup_key.
  • create_alert_channelCreate an alert channel.No findings

    Why it is in this group

    • The name "create_alert_channel" says "create": a word for a change.
    Description, as the server wrote it
    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_endpointCreate a new monitored endpoint.No findings

    Why it is in this group

    • The name "create_endpoint" says "create": a word for a change.
    Description, as the server wrote it
    Create a new monitored endpoint. Respects your tier's max_endpoints cap.
  • create_status_pageCreate a public status page at https://<slug>.status.monit.rs.No findings

    Why it is in this group

    • The name "create_status_page" says "create": a word for a change.
    Description, as the server wrote it
    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).
  • pause_endpointPause a monitored endpoint (stops probing, keeps history).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Pause a monitored endpoint (stops probing, keeps history). Idempotent — no-op if already paused.
  • resolve_incidentClose an incident.No findings

    Why it is in this group

    • The name "resolve_incident" says "resolve": a word for reading.
    • The description's first verb is "close": a word for a change.
    Description, as the server wrote it
    Close an incident. Symmetric to acknowledge_incident.
  • resume_endpointResume a paused endpoint.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Resume a paused endpoint. Rejects if resuming would exceed your tier's active-endpoint cap (upgrade or pause another endpoint first).
  • set_endpoint_assertionsReplace an endpoint's body assertions.No findings

    Why it is in this group

    • The name "set_endpoint_assertions" says "set": a word for a change.
    Description, as the server wrote it
    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_intervalChange how often an endpoint is probed.No findings

    Why it is in this group

    • The name "update_endpoint_interval" says "update": a word for a change.
    Description, as the server wrote it
    Change how often an endpoint is probed. Minimum interval varies by tier (free=900s, developer=300s, starter=60s, pro/scale/enterprise=30s).
Only reads 12Claude Code: allow
  • describe_endpointFull detail for one endpoint.No findings

    Why it is in this group

    • The name "describe_endpoint" says "describe": a word for reading.
    Description, as the server wrote it
    Full detail for one endpoint. Use `list_my_endpoints()` to get the ID.
  • describe_incidentFull detail for one incident.No findings

    Why it is in this group

    • The name "describe_incident" says "describe": a word for reading.
    Description, as the server wrote it
    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_uptimeAggregated uptime summary for an endpoint over the requested window.No findings

    Why it is in this group

    • The name "get_endpoint_uptime" says "get": a word for reading.
    Description, as the server wrote it
    Aggregated uptime summary for an endpoint over the requested window.
  • list_alert_channelsList alert channels configured on the authenticated account.No findings

    Why it is in this group

    • The name "list_alert_channels" says "list": a word for reading.
    Description, as the server wrote it
    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_endpointsList all monitored endpoints owned by the authenticated account.No findings

    Why it is in this group

    • The name "list_my_endpoints" says "list": a word for reading.
    Description, as the server wrote it
    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_incidentsList incidents on the caller's account.No findings

    Why it is in this group

    • The name "list_my_incidents" says "list": a word for reading.
    Description, as the server wrote it
    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_regressionsList detected schema regressions on the caller's account.No findings

    Why it is in this group

    • The name "list_my_regressions" says "list": a word for reading.
    Description, as the server wrote it
    List detected schema regressions on the caller's account. Optionally filter by endpoint_id.
  • list_security_findingsList security findings detected on the caller's monitored endpoints.No findings

    Why it is in this group

    • The name "list_security_findings" says "list": a word for reading.
    Description, as the server wrote it
    List security findings detected on the caller's monitored endpoints. Optionally filter by severity.
  • list_status_pagesList public status pages owned by the authenticated account.No findings

    Why it is in this group

    • The name "list_status_pages" says "list": a word for reading.
    Description, as the server wrote it
    List public status pages owned by the authenticated account.
  • monit_rs_describeReturn the canonical product description for monit.rs.No findings

    Why it is in this group

    • The name "monit_rs_describe" says "describe": a word for reading.
    Description, as the server wrote it
    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_statsGet live aggregate statistics for the monit.rs platform.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    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_diffCompare two OpenAPI 3.x specifications and classify every change as breaking, non-breaking, or info.No findings

    Why it is in this group

    • The name "openapi_diff" says "diff": a word for reading.
    Description, as the server wrote it
    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: [...]}.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__monit-rs__openapi_diff",
      "mcp__monit-rs__monit_rs_stats",
      "mcp__monit-rs__monit_rs_describe",
      "mcp__monit-rs__list_my_endpoints",
      "mcp__monit-rs__list_my_incidents",
      "mcp__monit-rs__list_my_regressions",
      "mcp__monit-rs__get_endpoint_uptime",
      "mcp__monit-rs__describe_endpoint",
      "mcp__monit-rs__list_alert_channels",
      "mcp__monit-rs__list_status_pages",
      "mcp__monit-rs__list_security_findings",
      "mcp__monit-rs__describe_incident"
    ],
    "ask": [
      "mcp__monit-rs__acknowledge_incident",
      "mcp__monit-rs__resolve_incident",
      "mcp__monit-rs__create_endpoint",
      "mcp__monit-rs__set_endpoint_assertions",
      "mcp__monit-rs__pause_endpoint",
      "mcp__monit-rs__resume_endpoint",
      "mcp__monit-rs__update_endpoint_interval",
      "mcp__monit-rs__create_status_page",
      "mcp__monit-rs__create_alert_channel"
    ],
    "deny": [
      "mcp__monit-rs__delete_endpoint"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as monit-rs. Review it before you use it.