monit-rs

Status

Newest check: answered with tools, from the daily check, 2026-10-05, 947 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-062026-10-05

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Documents and knowledge, ranked by days answering.

Tools

21 tools: 11 read-only, 9 change data, 1 high risk (delete, pay, send or run code).

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 2,855 tokens of tool definitions and a 947 ms handshake.

• high riskdelete_endpointDelete 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 un...
• changes dataopenapi_diffCompare 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 resp...
• changes datamonit_rs_statsGet 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.
• changes dataacknowledge_incidentMark an incident as acknowledged. Use `list_my_incidents()` to find the dedup_key.
• changes datacreate_endpointCreate a new monitored endpoint. Respects your tier's max_endpoints cap.
• changes datapause_endpointPause a monitored endpoint (stops probing, keeps history). Idempotent - no-op if already paused.
• changes dataresume_endpointResume a paused endpoint. Rejects if resuming would exceed your tier's active-endpoint cap (upgrade or pause another endpoint first).
• changes dataupdate_endpoint_intervalChange how often an endpoint is probed. Minimum interval varies by tier (free=900s, developer=300s, starter=60s, pro/scale/enterprise=30s).
• changes datacreate_status_pageCreate 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).
• changes datacreate_alert_channelCreate 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.s...
• read-onlymonit_rs_describeReturn 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.
• read-onlylist_my_endpointsList 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)`.
• read-onlylist_my_incidentsList 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.
• read-onlylist_my_regressionsList detected schema regressions on the caller's account. Optionally filter by endpoint_id.
• read-onlyget_endpoint_uptimeAggregated uptime summary for an endpoint over the requested window.
• read-onlydescribe_endpointFull detail for one endpoint. Use `list_my_endpoints()` to get the ID.
• read-onlyresolve_incidentClose an incident. Symmetric to acknowledge_incident.
• read-onlylist_alert_channelsList 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.
• read-onlylist_status_pagesList public status pages owned by the authenticated account.
• read-onlylist_security_findingsList security findings detected on the caller's monitored endpoints. Optionally filter by severity.
• read-onlydescribe_incidentFull detail for one incident. Use `list_my_incidents()` to find the dedup_key. Includes the incident's endpoint name and current status.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

What agents looked for

This week agents asked 7Maps for documents and knowledge servers 1 time; this server was shown 0 times and picked 0 times.

Owners see the keywords, the servers picked instead, failure reasons and a comparison with similar servers in Owner Insights.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/monit.rs/integrations/mcp.svg)](https://7it.co.il/7maps/s/monit.rs/integrations/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=monit.rs%2Fintegrations%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/monit.rs/integrations/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/monit.rs/integrations/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=monit.rs%2Fintegrations%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.