monit.rs

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as rs.monit/monit-rs and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 4 Oct 2026. Not supplied by the maker.

• 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 w

• 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. Us

• 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.

• 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_endpoin

• 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.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.