Combien d'outils expose rs.monit/monit-rs ?

rs.monit/monit-rs expose 22 outil(s). Le coût de contexte pour les charger tous est d'environ 3031 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / Communication / rs.monit/monit-rs

rs.monit/monit-rs

serveur MCP (Model Context Protocol) · monit.rs 1.28.1

▸ Communication

[ Non encore testé ]

Verdict MCP Hub
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.

streamable-httpType / transport

directAccès

~3031 tokensCoût de contexte

22Outils

Est-ce que rs.monit/monit-rs est sûr ?

Au dernier audit MCP Hub, le serveur MCP « rs.monit/monit-rs » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 22 outils

acknowledge_incident≈ 78 tokens
Mark an incident as acknowledged. Use `list_my_incidents()` to find the dedup_key.
Paramètres, retour & exemple (1)
Paramètres
- dedup_key · string · requis
Exemple d'appel
```
{"name": "acknowledge_incident", "arguments": {"dedup_key": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
create_alert_channel≈ 300 tokens
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='<Events v2 key>'
Paramètres, retour & exemple (5)
Paramètres
- webhook_url · ? · optionnel
- channel_type · string · requis · email | webhook | slack | pagerduty
- min_severity · string · optionnel · critical | high | medium | low | info
- email_address · ? · optionnel
- pagerduty_routing_key · ? · optionnel
Exemple d'appel
```
{"name": "create_alert_channel", "arguments": {"channel_type": "email"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
create_endpoint≈ 119 tokens
Create a new monitored endpoint. Respects your tier's max_endpoints cap.
Paramètres, retour & exemple (4)
Paramètres
- url · string · requis
- name · string · requis
- method · string · optionnel
- interval_seconds · integer · optionnel
Exemple d'appel
```
{"name": "create_endpoint", "arguments": {"url": "texte", "name": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
create_status_page≈ 151 tokens
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).
Paramètres, retour & exemple (3)
Paramètres
- slug · string · requis
- title · string · requis
- description · ? · optionnel
Exemple d'appel
```
{"name": "create_status_page", "arguments": {"slug": "texte", "title": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
delete_endpoint≈ 243 tokens
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.
Paramètres, retour & exemple (2)
Paramètres
- endpoint_id · string · requis
- confirm_by_typing_the_endpoint_name · string · requis
Exemple d'appel
```
{"name": "delete_endpoint", "arguments": {"endpoint_id": "texte", "confirm_by_typing_the_endpoint_name": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
describe_endpoint≈ 74 tokens
Full detail for one endpoint. Use `list_my_endpoints()` to get the ID.
Paramètres, retour & exemple (1)
Paramètres
- endpoint_id · string · requis
Exemple d'appel
```
{"name": "describe_endpoint", "arguments": {"endpoint_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
describe_incident≈ 90 tokens
Full detail for one incident. Use `list_my_incidents()` to find the dedup_key. Includes the incident's endpoint name and current status.
Paramètres, retour & exemple (1)
Paramètres
- dedup_key · string · requis
Exemple d'appel
```
{"name": "describe_incident", "arguments": {"dedup_key": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_endpoint_uptime≈ 100 tokens
Aggregated uptime summary for an endpoint over the requested window.
Paramètres, retour & exemple (2)
Paramètres
- window · string · optionnel · 24h | 7d | 30d | 90d
- endpoint_id · string · requis
Exemple d'appel
```
{"name": "get_endpoint_uptime", "arguments": {"endpoint_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
list_alert_channels≈ 156 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "list_alert_channels", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}
```
list_my_endpoints≈ 144 tokens
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)`.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "list_my_endpoints", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}
```
list_my_incidents≈ 184 tokens
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.
Paramètres, retour & exemple (2)
Paramètres
- limit · integer · optionnel
- status · string · optionnel · open | acknowledged | resolved
Exemple d'appel
```
{"name": "list_my_incidents", "arguments": {"limit": 1, "status": "open"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}
```
list_my_regressions≈ 157 tokens
List detected schema regressions on the caller's account. Optionally filter by endpoint_id.
Paramètres, retour & exemple (2)
Paramètres
- limit · integer · optionnel
- endpoint_id · ? · optionnel
Exemple d'appel
```
{"name": "list_my_regressions", "arguments": {"limit": 1, "endpoint_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}
```
list_security_findings≈ 174 tokens
List security findings detected on the caller's monitored endpoints. Optionally filter by severity.
Paramètres, retour & exemple (2)
Paramètres
- limit · integer · optionnel
- severity · ? · optionnel
Exemple d'appel
```
{"name": "list_security_findings", "arguments": {"limit": 1, "severity": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}
```
list_status_pages≈ 105 tokens
List public status pages owned by the authenticated account.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "list_status_pages", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}
```
monit_rs_describe≈ 154 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "monit_rs_describe", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}
```
monit_rs_stats≈ 166 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "monit_rs_stats", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": {}}}
```
openapi_diff≈ 248 tokens
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: [...]}.
Paramètres, retour & exemple (2)
Paramètres
- new_spec · string · requis
- old_spec · string · requis
Exemple d'appel
```
{"name": "openapi_diff", "arguments": {"new_spec": "texte", "old_spec": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": {}}}
```
pause_endpoint≈ 80 tokens
Pause a monitored endpoint (stops probing, keeps history). Idempotent — no-op if already paused.
Paramètres, retour & exemple (1)
Paramètres
- endpoint_id · string · requis
Exemple d'appel
```
{"name": "pause_endpoint", "arguments": {"endpoint_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
resolve_incident≈ 68 tokens
Close an incident. Symmetric to acknowledge_incident.
Paramètres, retour & exemple (1)
Paramètres
- dedup_key · string · requis
Exemple d'appel
```
{"name": "resolve_incident", "arguments": {"dedup_key": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
resume_endpoint≈ 90 tokens
Resume a paused endpoint. Rejects if resuming would exceed your tier's active-endpoint cap (upgrade or pause another endpoint first).
Paramètres, retour & exemple (1)
Paramètres
- endpoint_id · string · requis
Exemple d'appel
```
{"name": "resume_endpoint", "arguments": {"endpoint_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
set_endpoint_assertions≈ 178 tokens
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.
Paramètres, retour & exemple (2)
Paramètres
- assertions · array · requis
- endpoint_id · string · requis
Exemple d'appel
```
{"name": "set_endpoint_assertions", "arguments": {"assertions": [], "endpoint_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
update_endpoint_interval≈ 118 tokens
Change how often an endpoint is probed. Minimum interval varies by tier (free=900s, developer=300s, starter=60s, pro/scale/enterprise=30s).
Paramètres, retour & exemple (2)
Paramètres
- endpoint_id · string · requis
- interval_seconds · integer · requis
Exemple d'appel
```
{"name": "update_endpoint_interval", "arguments": {"endpoint_id": "texte", "interval_seconds": 1}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://monit.rs/integrations/mcp