monit.rs is an MCP server with 22 tools an agent can call, among them acknowledge_incident, create_alert_channel, create_endpoint. It answers at https://monit.rs/integrations/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 5 October 2026; the last check, on 21 November 2026, succeeded.
Schema-aware API monitoring: diff OpenAPI specs for breaking changes, manage endpoints.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
acknowledge_incident | Mark an incident as acknowledged. Use `list_my_incidents()` to find the dedup_key. Inputs: 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='[email protected]' - channel_type='webhook' → webhook_url='https://your-endpoi Inputs: channel_type, email_address, webhook_url, pagerduty_routing_key, min_severity |
create_endpoint | Create a new monitored endpoint. Respects your tier's max_endpoints cap. Inputs: name, url, method, 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). Inputs: slug, title, description |
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 `.n Inputs: endpoint_id, confirm_by_typing_the_endpoint_name |
describe_endpoint | Full detail for one endpoint. Use `list_my_endpoints()` to get the ID. Inputs: endpoint_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. Inputs: dedup_key |
get_endpoint_uptime | Aggregated uptime summary for an endpoint over the requested window. Inputs: endpoint_id, 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. Inputs: status, limit |
list_my_regressions | List detected schema regressions on the caller's account. Optionally filter by endpoint_id. Inputs: endpoint_id, limit |
list_security_findings | List security findings detected on the caller's monitored endpoints. Optionally filter by severity. Inputs: severity, limit |
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/llm |
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 s |
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, op Inputs: old_spec, new_spec |
pause_endpoint | Pause a monitored endpoint (stops probing, keeps history). Idempotent — no-op if already paused. Inputs: endpoint_id |
resolve_incident | Close an incident. Symmetric to acknowledge_incident. Inputs: dedup_key |
resume_endpoint | Resume a paused endpoint. Rejects if resuming would exceed your tier's active-endpoint cap (upgrade or pause another endpoint first). Inputs: endpoint_id |
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 mar Inputs: endpoint_id, assertions |
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). Inputs: endpoint_id, interval_seconds |
Every block below points at https://monit.rs/integrations/mcp. Pick your client and copy.
claude mcp add --transport http monit-rs https://monit.rs/integrations/mcp
{
"mcpServers": {
"monit-rs": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://monit.rs/integrations/mcp"]
}
}
}{
"mcpServers": {
"monit-rs": {
"url": "https://monit.rs/integrations/mcp"
}
}
}{
"servers": {
"monit-rs": {
"type": "http",
"url": "https://monit.rs/integrations/mcp"
}
}
}{
"context_servers": {
"monit-rs": {
"url": "https://monit.rs/integrations/mcp"
}
}
}{
"mcpServers": {
"monit-rs": {
"serverUrl": "https://monit.rs/integrations/mcp"
}
}
}{
"mcpServers": {
"monit-rs": {
"url": "https://monit.rs/integrations/mcp"
}
}
}name: monit.rs
version: 0.0.1
schema: v1
mcpServers:
- name: monit.rs
type: streamable-http
url: https://monit.rs/integrations/mcp{
"mcpServers": {
"monit-rs": {
"httpUrl": "https://monit.rs/integrations/mcp"
}
}
}{
"mcpServers": {
"monit-rs": {
"type": "http",
"url": "https://monit.rs/integrations/mcp"
}
}
}{
"mcpServers": {
"monit-rs": {
"url": "https://monit.rs/integrations/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmonit.rs%2Fintegrations%2Fmcp&type=streamable_http&id=monit-rs&name=monit.rs
It answered our last check on 21 November 2026 in 685 ms. Over 4 checks since 5 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by monit.rs and served from monit.rs, the vendor's own domain: https://monit.rs/integrations/mcp.
22, as returned by the server's own tools/list on 21 November 2026: acknowledge_incident, create_alert_channel, create_endpoint, create_status_page, delete_endpoint, describe_endpoint, describe_incident, get_endpoint_uptime, and 14 more.
It answered our last check on 21 November 2026 in 685 ms. Over 4 checks since 5 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://monit.rs/integrations/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: rs.monit. Endpoint host: monit.rs. ARD identifier: urn:air:rs.monit:mcp:monit-rs.
First indexed 4 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.