Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Nothing to run from here
monit.rs is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
21
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Schema-aware API monitoring: diff OpenAPI specs for breaking changes, manage endpoints.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http monit-rs-mcp https://monit.rs/integrations/mcp
# 2 — ask your agent for something these tools do
# openapi_diff, monit_rs_stats, monit_rs_describe and 18 more
monit.rs costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MOAll 1 server
monit1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http monit-rs-mcp https://monit.rs/integrations/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| old_spec | string | yes | — |
| new_spec | string | yes | — |
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.
No parameter schema on file.
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.
No parameter schema on file.
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).
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | — |
| limit | integer | no | — |
List detected schema regressions on the caller's account. Optionally filter by endpoint_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | no | — | |
| limit | integer | no | — |
Aggregated uptime summary for an endpoint over the requested window.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | string | yes | — |
| window | string | no | — |
Full detail for one endpoint. Use list_my_endpoints() to get the ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | string | yes | — |
Mark an incident as acknowledged. Use list_my_incidents() to find the dedup_key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dedup_key | string | yes | — |
Close an incident. Symmetric to acknowledge_incident.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dedup_key | string | yes | — |
Create a new monitored endpoint. Respects your tier's max_endpoints cap.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| url | string | yes | — |
| method | string | no | — |
| interval_seconds | integer | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | string | yes | — |
| confirm_by_typing_the_endpoint_name | string | yes | — |
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.
No parameter schema on file.
List public status pages owned by the authenticated account.
No parameter schema on file.
List security findings detected on the caller's monitored endpoints. Optionally filter by severity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| severity | no | — | |
| limit | integer | no | — |
Full detail for one incident. Use list_my_incidents() to find the dedup_key. Includes the incident's endpoint name and current status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dedup_key | string | yes | — |
Pause a monitored endpoint (stops probing, keeps history). Idempotent — no-op if already paused.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | string | yes | — |
Resume a paused endpoint. Rejects if resuming would exceed your tier's active-endpoint cap (upgrade or pause another endpoint first).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | string | yes | — |
Change how often an endpoint is probed. Minimum interval varies by tier (free=900s, developer=300s, starter=60s, pro/scale/enterprise=30s).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint_id | string | yes | — |
| interval_seconds | integer | yes | — |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| title | string | yes | — |
| description | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel_type | string | yes | — |
| email_address | no | — | |
| webhook_url | no | — | |
| pagerduty_routing_key | no | — | |
| min_severity | string | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install monit.rs or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
0.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish monit.rs can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.