Connect-MCP

monit.rs

rs.monit/monit-rs · v0.2.0

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

MCPremoteno credentialsCloud & DevOps

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 22 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 75/100

What it does: 22 tools · 10 read, 6 write (incl. delete/pay)

Test call list_my_endpoints: needs a key: tool error: Error executing tool list_my_endpoints: [authentication_required] Set 'Authorization: Bearer mrs_live_...' in your MCP t (889 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +2
  • Read/write annotations: 0
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://monit.rs/integrations/mcp

Tools

22 tools listed at last check
  • 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, respo
  • 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
  • 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 descri
  • 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
  • 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-trimme
  • 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='[email protected]' - channel_type='webhook' → webhook_url='https://your-endpoint' - channel_type='slack'

Badge

Connect-MCP badge for rs.monit/monit-rs

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/rs.monit/monit-rs.svg)](https://clawy.uk/mcp/s/rs.monit/monit-rs)

Website