monit.rs MCP Server

by monit Your server? Claim it

answering

monit.rs is answering right now. Last checked 14 min ago. It exposes 22 tools.

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

Uptime history 21 days of history · worst day 97%

21 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

851 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 October 2026. No other catalogue keeps this.

15 Oct a tool appeared set_endpoint_assertions

monit.rs missed 3 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add monit-rs --transport http https://monit.rs/integrations/mcp

Settings → Connectors → Add custom connector, then paste this address

https://monit.rs/integrations/mcp

~/.codex/config.toml

[mcp_servers.monit-rs]
url = "https://monit.rs/integrations/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "monit-rs": {
      "url": "https://monit.rs/integrations/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "monit-rs": {
      "type": "http",
      "url": "https://monit.rs/integrations/mcp"
    }
  }
}

Available tools 22

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

endpoint

create_endpoint

Create a new monitored endpoint. Respects your tier's max_endpoints cap.

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 `describe_endpoint(id)` to learn the name, then include it verbatim. 2. Per-user destructive-op cap of 5/day. Legitimate bulk deletes should use the HTTP API or dashboard.

get_endpoint_uptime

Aggregated uptime summary for an endpoint over the requested window.

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.

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

alert

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' → webhook_url='https://hooks.slack.com/...' - channel_type='pagerduty' → pagerduty_routing_key='<Events v2 key>'

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.

describe

describe_endpoint

Full detail for one endpoint. Use `list_my_endpoints()` to get the 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.

monit

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.

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.

status

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

list_status_pages

List public status pages owned by the authenticated account.

acknowledge

acknowledge_incident

Mark an incident as acknowledged. Use `list_my_incidents()` to find the dedup_key.

endpoints

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)`.

incidents

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.

openapi

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 arguments are the OpenAPI spec as a JSON or YAML string. Returns {summary: {breaking, non_breaking, info}, changes: [...]}.

pause

pause_endpoint

Pause a monitored endpoint (stops probing, keeps history). Idempotent — no-op if already paused.

regressions

list_my_regressions

List detected schema regressions on the caller's account. Optionally filter by endpoint_id.

resolve

resolve_incident

Close an incident. Symmetric to acknowledge_incident.

resume

resume_endpoint

Resume a paused endpoint. Rejects if resuming would exceed your tier's active-endpoint cap (upgrade or pause another endpoint first).

security

list_security_findings

List security findings detected on the caller's monitored endpoints. Optionally filter by severity.

Endpoints

URL	Transport	State	Latency	Checked
https://monit.rs/integrations/mcp	streamable-http	answering	820 ms	14 min ago

Alternatives to monit.rs

same job, measured the same way

Schemaguard

by sethclawd-prog

API Schema Drift Monitor — detect breaking changes in OpenAPI specs

20 installs/wk local only

Fixzi — MCP & API Schema Drift Monitor

by rohitcodilya

Monitor MCP servers, API contracts and AI outputs for schema drift. Alerts on breaking changes.

answering

Scout Monitoring

by scoutapm

Scout Monitoring data for AI assistants: slow endpoints, traces, N+1 queries, and errors.

answering

Scopeguard

by alex-dev-web-c-de

Sanctions scope monitoring. Track entities for changes in OFAC/UK/EU/UN lists.

273 installs/wk local only

Website Change Monitor

by blyck

Monitor public pages and JSON endpoints after agents disconnect, with polling and webhooks.

answering

Competiflow MCP

by nyku

Competitor monitoring for AI agents: track rival pricing, docs and changelog changes with evidence.

4 installs/wk local only

Safeship

by safeship

API monitoring from your editor. Checks the JSON your endpoints return, not just the status code.

answering

PageRadar

by pageradar

Monitor web pages for changes: create monitors, list detected changes and read diffs.

answering

monit.rs — questions

Answers built from our own checks of this server.

What can monit.rs do?

It exposes 22 tools, read directly from the server on our last check. Among them: acknowledge_incident, create_alert_channel, create_endpoint, create_status_page, delete_endpoint, describe_endpoint and 16 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is monit.rs mostly used for?

Its tools cluster around endpoint, describe and monit. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is monit.rs working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 851 ms. The bar chart above shows every period we have measured.

How do I connect monit.rs?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does monit.rs need an API key?

No. monit.rs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 22 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is monit.rs?

It answers our handshake in 851 ms on average, which is faster than 10% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.