_ registry / mcp http-sse · checked 1h ago

monit.rs

https://monit.rs

Registry code: c546675fdd272f3b

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://monit.rs/integrations/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is monit.rs live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is monit.rs free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does monit.rs have?
22 tools: pause_endpoint, acknowledge_incident, create_endpoint, set_endpoint_assertions, resume_endpoint, create_status_page, get_endpoint_uptime, describe_endpoint, ….
Is monit.rs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 98.8%· all time 98.8%

latency
729ms

last good check

priced tools
0

of 22 tools

_ answered our checks, 90 days 344 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • monitor api endpoints for uptime
  • diff openapi specs for breaking changes
  • manage incidents and alerts
  • create a public status page
takes → gives
text, data, code → data
tools
12 reads9 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 22 tools
2 open6 auth-required 14 never probed 8 of 22 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • monit_rs_describe reads open 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "monit_rs_describeArguments",
      "properties": {}
    }
    arguments 5 lines
  • monit_rs_stats reads open 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "monit_rs_statsArguments",
      "properties": {}
    }
    arguments 5 lines
  • list_my_incidents reads auth-required 21h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "list_my_incidentsArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 20
        },
        "status": {
          "enum": [
            "open",
            "acknowledged",
            "resolved"
          ],
          "type": "string",
          "title": "Status",
          "default": "open"
        }
      }
    }
    arguments 21 lines
  • list_my_regressions reads auth-required 21h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "list_my_regressionsArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 20
        },
        "endpoint_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Endpoint Id",
          "default": null
        }
      }
    }
    arguments 23 lines
  • list_my_endpoints reads auth-required 21h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "list_my_endpointsArguments",
      "properties": {}
    }
    arguments 5 lines
  • list_security_findings reads auth-required 15h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "list_security_findingsArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 20
        },
        "severity": {
          "anyOf": [
            {
              "enum": [
                "critical",
                "high",
                "medium",
                "low",
                "info"
              ],
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Severity",
          "default": null
        }
      }
    }
    arguments 30 lines
  • list_status_pages reads auth-required 15h ago

    List public status pages owned by the authenticated account.

    mcp-tool

    {
      "type": "object",
      "title": "list_status_pagesArguments",
      "properties": {}
    }
    arguments 5 lines
  • list_alert_channels reads auth-required 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "list_alert_channelsArguments",
      "properties": {}
    }
    arguments 5 lines
  • pause_endpoint changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "title": "pause_endpointArguments",
      "required": [
        "endpoint_id"
      ],
      "properties": {
        "endpoint_id": {
          "type": "string",
          "title": "Endpoint Id"
        }
      }
    }
    arguments 13 lines
  • acknowledge_incident changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "title": "acknowledge_incidentArguments",
      "required": [
        "dedup_key"
      ],
      "properties": {
        "dedup_key": {
          "type": "string",
          "title": "Dedup Key"
        }
      }
    }
    arguments 13 lines
  • create_endpoint changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "title": "create_endpointArguments",
      "required": [
        "name",
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Url"
        },
        "name": {
          "type": "string",
          "title": "Name"
        },
        "method": {
          "type": "string",
          "title": "Method",
          "default": "GET"
        },
        "interval_seconds": {
          "type": "integer",
          "title": "Interval Seconds",
          "default": 900
        }
      }
    }
    arguments 28 lines
  • set_endpoint_assertions unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "set_endpoint_assertionsArguments",
      "required": [
        "endpoint_id",
        "assertions"
      ],
      "properties": {
        "assertions": {
          "type": "array",
          "items": {
            "type": "object",
            "additionalProperties": true
          },
          "title": "Assertions"
        },
        "endpoint_id": {
          "type": "string",
          "title": "Endpoint Id"
        }
      }
    }
    arguments 22 lines
  • resume_endpoint changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "title": "resume_endpointArguments",
      "required": [
        "endpoint_id"
      ],
      "properties": {
        "endpoint_id": {
          "type": "string",
          "title": "Endpoint Id"
        }
      }
    }
    arguments 13 lines
  • create_status_page changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "title": "create_status_pageArguments",
      "required": [
        "slug",
        "title"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "title": "Slug"
        },
        "title": {
          "type": "string",
          "title": "Title"
        },
        "description": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Description",
          "default": null
        }
      }
    }
    arguments 30 lines
  • get_endpoint_uptime reads unknown 1h ago

    Aggregated uptime summary for an endpoint over the requested window.

    mcp-tool

    {
      "type": "object",
      "title": "get_endpoint_uptimeArguments",
      "required": [
        "endpoint_id"
      ],
      "properties": {
        "window": {
          "enum": [
            "24h",
            "7d",
            "30d",
            "90d"
          ],
          "type": "string",
          "title": "Window",
          "default": "7d"
        },
        "endpoint_id": {
          "type": "string",
          "title": "Endpoint Id"
        }
      }
    }
    arguments 24 lines
  • describe_endpoint reads unknown 1h ago

    Full detail for one endpoint. Use `list_my_endpoints()` to get the ID.

    mcp-tool

    {
      "type": "object",
      "title": "describe_endpointArguments",
      "required": [
        "endpoint_id"
      ],
      "properties": {
        "endpoint_id": {
          "type": "string",
          "title": "Endpoint Id"
        }
      }
    }
    arguments 13 lines
  • resolve_incident changes data unknown never probed

    Close an incident. Symmetric to acknowledge_incident.

    mcp-tool

    {
      "type": "object",
      "title": "resolve_incidentArguments",
      "required": [
        "dedup_key"
      ],
      "properties": {
        "dedup_key": {
          "type": "string",
          "title": "Dedup Key"
        }
      }
    }
    arguments 13 lines
  • delete_endpoint changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "delete_endpointArguments",
      "required": [
        "endpoint_id",
        "confirm_by_typing_the_endpoint_name"
      ],
      "properties": {
        "endpoint_id": {
          "type": "string",
          "title": "Endpoint Id"
        },
        "confirm_by_typing_the_endpoint_name": {
          "type": "string",
          "title": "Confirm By Typing The Endpoint Name"
        }
      }
    }
    arguments 18 lines
  • update_endpoint_interval changes data unknown never probed

    Change how often an endpoint is probed. Minimum interval varies by tier (free=900s, developer=300s, starter=60s, pro/scale/enterprise=30s).

    mcp-tool

    {
      "type": "object",
      "title": "update_endpoint_intervalArguments",
      "required": [
        "endpoint_id",
        "interval_seconds"
      ],
      "properties": {
        "endpoint_id": {
          "type": "string",
          "title": "Endpoint Id"
        },
        "interval_seconds": {
          "type": "integer",
          "title": "Interval Seconds"
        }
      }
    }
    arguments 18 lines
  • describe_incident reads unknown 15h ago

    Full detail for one incident. Use `list_my_incidents()` to find the dedup_key. Includes the incident's endpoint name and current status.

    mcp-tool

    {
      "type": "object",
      "title": "describe_incidentArguments",
      "required": [
        "dedup_key"
      ],
      "properties": {
        "dedup_key": {
          "type": "string",
          "title": "Dedup Key"
        }
      }
    }
    arguments 13 lines
  • openapi_diff reads unknown never probed

    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: [...]}.

    mcp-tool

    {
      "type": "object",
      "title": "openapi_diffArguments",
      "required": [
        "old_spec",
        "new_spec"
      ],
      "properties": {
        "new_spec": {
          "type": "string",
          "title": "New Spec"
        },
        "old_spec": {
          "type": "string",
          "title": "Old Spec"
        }
      }
    }
    arguments 18 lines
  • create_alert_channel changes data unknown never probed

    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>'

    mcp-tool

    {
      "type": "object",
      "title": "create_alert_channelArguments",
      "required": [
        "channel_type"
      ],
      "properties": {
        "webhook_url": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Webhook Url",
          "default": null
        },
        "channel_type": {
          "enum": [
            "email",
            "webhook",
            "slack",
            "pagerduty"
          ],
          "type": "string",
          "title": "Channel Type"
        },
        "min_severity": {
          "enum": [
            "critical",
            "high",
            "medium",
            "low",
            "info"
          ],
          "type": "string",
          "title": "Min Severity",
          "default": "medium"
        },
        "email_address": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Email Address",
          "default": null
        },
        "pagerduty_routing_key": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Pagerduty Routing Key",
          "default": null
        }
      }
    }
    arguments 67 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c546675fdd272f3b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c546675fdd272f3b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c546675fdd272f3b/badge.svg)](https://brick.blue/agent/c546675fdd272f3b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.