monit.rs
Schema-aware API monitoring: diff OpenAPI specs for breaking changes, manage endpoints.
| Endpoint | https://monit.rs/integrations/mcp (streamable-http) |
|---|---|
| Registry version | 0.2.0 |
| Now | 22 tools · grade C (74) · pin ts_f537722663630daef87e23fa292b50d2 · protocol 2025-06-18 |
| First / last listed | 2026-11-02 02:22 UTC / 2026-11-02 02:22 UTC |
| Grade over time | 2026-11-02: C (74), 22 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: openapi_diff monit_rs_stats monit_rs_describe list_my_endpoints list_my_incidents list_my_regressions get_endpoint_uptime describe_endpoint acknowledge_incident resolve_incident create_endpoint set_endpoint_assertions delete_endpoint list_alert_channels list_status_pages list_security_findings describe_incident pause_endpoint resume_endpoint update_endpoint_interval create_status_page create_alert_channel
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 argume params: old_spec*, new_spec* |
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.
params: none |
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.
params: none |
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)`.
params: none |
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.
params: status, limit |
list_my_regressions | List detected schema regressions on the caller's account.
Optionally filter by endpoint_id. params: endpoint_id, limit |
get_endpoint_uptime | Aggregated uptime summary for an endpoint over the requested window. params: endpoint_id*, window |
describe_endpoint | Full detail for one endpoint. Use `list_my_endpoints()` to get the ID. params: endpoint_id* |
acknowledge_incident | Mark an incident as acknowledged. Use `list_my_incidents()` to
find the dedup_key. params: dedup_key* |
resolve_incident | Close an incident. Symmetric to acknowledge_incident. params: dedup_key* |
create_endpoint | Create a new monitored endpoint. Respects your tier's max_endpoints cap. params: name*, url*, method, interval_seconds |
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.
params: endpoint_id*, assertions* |
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 `descr params: endpoint_id*, confirm_by_typing_the_endpoint_name* |
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.
params: none |
list_status_pages | List public status pages owned by the authenticated account. params: none |
list_security_findings | List security findings detected on the caller's monitored endpoints.
Optionally filter by severity. params: severity, limit |
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. params: dedup_key* |
pause_endpoint | Pause a monitored endpoint (stops probing, keeps history). Idempotent
— no-op if already paused. params: endpoint_id* |
resume_endpoint | Resume a paused endpoint. Rejects if resuming would exceed your tier's
active-endpoint cap (upgrade or pause another endpoint first). params: endpoint_id* |
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). params: endpoint_id*, interval_seconds* |
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). params: slug*, title*, description |
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 params: channel_type*, email_address, webhook_url, pagerduty_routing_key, min_severity |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.