MCP MeasureMCP Measure

インデックス観測済み

monit.rs

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

使うべきか

品質と安全性

B
説明の品質
96%
スキーマの完全性
65%
命名の品質
94%
ポイズニングのリスク
80%
権限の一致
100%
プロトコルへの準拠
100%

検出事項（2）

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domaincreate_alert_channel 内

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~2,667トークン数（ツール定義）
~818 B一般的なレスポンスサイズ
注意への影響は大きい（128k コンテキストの 2.08%）

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

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

リモートエンドポイント

https://monit.rs/integrations/mcpstreamable-http

できること

ツール一覧

ツール（21）

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟡openapi_diff(old_spec, new_spec)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "old_spec": {
      "title": "Old Spec",
      "type": "string"
    },
    "new_spec": {
      "title": "New Spec",
      "type": "string"
    }
  },
  "required": [
    "old_spec",
    "new_spec"
  ],
  "title": "openapi_diffArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "additionalProperties": true,
      "title": "Result",
      "type": "object"
    }
  },
  "required": [
    "result"
  ],
  "title": "openapi_diffOutput"
}
🟢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.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "title": "monit_rs_statsArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "additionalProperties": {
        "type": "integer"
      },
      "title": "Result",
      "type": "object"
    }
  },
  "required": [
    "result"
  ],
  "title": "monit_rs_statsOutput"
}
🟢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.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "title": "monit_rs_describeArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "title": "Result",
      "type": "string"
    }
  },
  "required": [
    "result"
  ],
  "title": "monit_rs_describeOutput"
}
🟢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)`.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "title": "list_my_endpointsArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "title": "Result",
      "type": "array"
    }
  },
  "required": [
    "result"
  ],
  "title": "list_my_endpointsOutput"
}
🟢list_my_incidents(status, limit)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "status": {
      "default": "open",
      "enum": [
        "open",
        "acknowledged",
        "resolved"
      ],
      "title": "Status",
      "type": "string"
    },
    "limit": {
      "default": 20,
      "title": "Limit",
      "type": "integer"
    }
  },
  "title": "list_my_incidentsArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "title": "Result",
      "type": "array"
    }
  },
  "required": [
    "result"
  ],
  "title": "list_my_incidentsOutput"
}
🟢list_my_regressions(endpoint_id, limit)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Endpoint Id"
    },
    "limit": {
      "default": 20,
      "title": "Limit",
      "type": "integer"
    }
  },
  "title": "list_my_regressionsArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "title": "Result",
      "type": "array"
    }
  },
  "required": [
    "result"
  ],
  "title": "list_my_regressionsOutput"
}
🟢get_endpoint_uptime(endpoint_id, window)

Aggregated uptime summary for an endpoint over the requested window.

入力スキーマ

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "title": "Endpoint Id",
      "type": "string"
    },
    "window": {
      "default": "7d",
      "enum": [
        "24h",
        "7d",
        "30d",
        "90d"
      ],
      "title": "Window",
      "type": "string"
    }
  },
  "required": [
    "endpoint_id"
  ],
  "title": "get_endpoint_uptimeArguments"
}
🟢describe_endpoint(endpoint_id)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "title": "Endpoint Id",
      "type": "string"
    }
  },
  "required": [
    "endpoint_id"
  ],
  "title": "describe_endpointArguments"
}
🟢acknowledge_incident(dedup_key)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "dedup_key": {
      "title": "Dedup Key",
      "type": "string"
    }
  },
  "required": [
    "dedup_key"
  ],
  "title": "acknowledge_incidentArguments"
}
⚪resolve_incident(dedup_key)

Close an incident. Symmetric to acknowledge_incident.

入力スキーマ

{
  "type": "object",
  "properties": {
    "dedup_key": {
      "title": "Dedup Key",
      "type": "string"
    }
  },
  "required": [
    "dedup_key"
  ],
  "title": "resolve_incidentArguments"
}
🟡create_endpoint(name, url, method, interval_seconds)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "name": {
      "title": "Name",
      "type": "string"
    },
    "url": {
      "title": "Url",
      "type": "string"
    },
    "method": {
      "default": "GET",
      "title": "Method",
      "type": "string"
    },
    "interval_seconds": {
      "default": 900,
      "title": "Interval Seconds",
      "type": "integer"
    }
  },
  "required": [
    "name",
    "url"
  ],
  "title": "create_endpointArguments"
}
🔴delete_endpoint(endpoint_id, confirm_by_typing_the_endpoint_name)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "title": "Endpoint Id",
      "type": "string"
    },
    "confirm_by_typing_the_endpoint_name": {
      "title": "Confirm By Typing The Endpoint Name",
      "type": "string"
    }
  },
  "required": [
    "endpoint_id",
    "confirm_by_typing_the_endpoint_name"
  ],
  "title": "delete_endpointArguments"
}
🟢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.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "title": "list_alert_channelsArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "title": "Result",
      "type": "array"
    }
  },
  "required": [
    "result"
  ],
  "title": "list_alert_channelsOutput"
}
🟢list_status_pages

List public status pages owned by the authenticated account.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "title": "list_status_pagesArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "title": "Result",
      "type": "array"
    }
  },
  "required": [
    "result"
  ],
  "title": "list_status_pagesOutput"
}
🟢list_security_findings(severity, limit)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "severity": {
      "anyOf": [
        {
          "enum": [
            "critical",
            "high",
            "medium",
            "low",
            "info"
          ],
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Severity"
    },
    "limit": {
      "default": 20,
      "title": "Limit",
      "type": "integer"
    }
  },
  "title": "list_security_findingsArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "title": "Result",
      "type": "array"
    }
  },
  "required": [
    "result"
  ],
  "title": "list_security_findingsOutput"
}
🟢describe_incident(dedup_key)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "dedup_key": {
      "title": "Dedup Key",
      "type": "string"
    }
  },
  "required": [
    "dedup_key"
  ],
  "title": "describe_incidentArguments"
}
⚪pause_endpoint(endpoint_id)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "title": "Endpoint Id",
      "type": "string"
    }
  },
  "required": [
    "endpoint_id"
  ],
  "title": "pause_endpointArguments"
}
⚪resume_endpoint(endpoint_id)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "title": "Endpoint Id",
      "type": "string"
    }
  },
  "required": [
    "endpoint_id"
  ],
  "title": "resume_endpointArguments"
}
🟡update_endpoint_interval(endpoint_id, interval_seconds)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "title": "Endpoint Id",
      "type": "string"
    },
    "interval_seconds": {
      "title": "Interval Seconds",
      "type": "integer"
    }
  },
  "required": [
    "endpoint_id",
    "interval_seconds"
  ],
  "title": "update_endpoint_intervalArguments"
}
🟡create_status_page(slug, title, description)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "slug": {
      "title": "Slug",
      "type": "string"
    },
    "title": {
      "title": "Title",
      "type": "string"
    },
    "description": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Description"
    }
  },
  "required": [
    "slug",
    "title"
  ],
  "title": "create_status_pageArguments"
}
🟡create_alert_channel(channel_type, email_address, webhook_url, pagerduty_routing_key, min_severity)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "channel_type": {
      "enum": [
        "email",
        "webhook",
        "slack",
        "pagerduty"
      ],
      "title": "Channel Type",
      "type": "string"
    },
    "email_address": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Email Address"
    },
    "webhook_url": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Webhook Url"
    },
    "pagerduty_routing_key": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Pagerduty Routing Key"
    },
    "min_severity": {
      "default": "medium",
      "enum": [
        "critical",
        "high",
        "medium",
        "low",
        "info"
      ],
      "title": "Min Severity",
      "type": "string"
    }
  },
  "required": [
    "channel_type"
  ],
  "title": "create_alert_channelArguments"
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 21 件