MCP MeasureMCP Measure

Index beobachtet

betterstack

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

Sollte ich dies verwenden

Qualität und Sicherheit

A
Qualität der Beschreibung
100%
Vollständigkeit des Schemas
94%
Qualität der Benennung
96%
Risiko der Vergiftung
80%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Befunde (2)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains suspicious base64-like encoded stringin list_monitors

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~1,611Tokens (Tool-Definitionen)
~1.3 KBTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (1.26% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "betterstack": {
      "url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}

Remote-Endpunkte

https://betterstack.usefulapi.io/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (9)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢list_monitors(url, pronounceable_name, team_name, page, per_page)

List uptime monitors with their status (up/down/paused/pending/maintenance/validating), check frequency, and alert settings. Good first call to discover what is being monitored. Uptime API: GET /api/v2/monitors.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "url": {
      "description": "Filter monitors by their monitored URL.",
      "type": "string"
    },
    "pronounceable_name": {
      "description": "Filter monitors by their pronounceable name.",
      "type": "string"
    },
    "team_name": {
      "description": "Filter by team name (only when using a global API token).",
      "type": "string"
    },
    "page": {
      "description": "Page number for pagination (default 1).",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "per_page": {
      "description": "Results per page.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 250
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_monitor(monitor_id)

Get a single monitor by id, including current status, last_checked_at, SSL/HTTP settings, regions, and alerting configuration. Uptime API: GET /api/v2/monitors/{id}.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "monitor_id": {
      "type": "string",
      "description": "The monitor id (from list_monitors)."
    }
  },
  "required": [
    "monitor_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_incidents(from, to, monitor_id, heartbeat_id, resolved, ...)

List incidents (alerts triggered by monitors/heartbeats), filterable by date range, monitor, and acknowledged/resolved state. Each incident carries cause, started_at, acknowledged_at, resolved_at. Uptime API: GET /api/v3/incidents.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "from": {
      "description": "Start date yyyy-mm-dd (inclusive).",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "to": {
      "description": "End date yyyy-mm-dd (inclusive).",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "monitor_id": {
      "description": "Only incidents for this monitor id.",
      "type": "string"
    },
    "heartbeat_id": {
      "description": "Only incidents for this heartbeat id.",
      "type": "string"
    },
    "resolved": {
      "description": "true = only resolved, false = only unresolved.",
      "type": "boolean"
    },
    "acknowledged": {
      "description": "true = only acknowledged, false = only unacknowledged.",
      "type": "boolean"
    },
    "team_name": {
      "description": "Filter by team name (only when using a global API token).",
      "type": "string"
    },
    "page": {
      "description": "Page number for pagination (default 1).",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "per_page": {
      "description": "Results per page.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 250
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_incident(incident_id)

Get a single incident by id, including cause, status, timeline timestamps (started/acknowledged/resolved), who acknowledged/resolved it, and the related monitor. Uptime API: GET /api/v3/incidents/{id}.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "incident_id": {
      "type": "string",
      "description": "The incident id (from list_incidents)."
    }
  },
  "required": [
    "incident_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_heartbeats(team_name, page, per_page)

List heartbeats (cron/background-job monitors that expect a periodic ping), with period, grace, and status (up/down/paused/pending). Uptime API: GET /api/v2/heartbeats.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "team_name": {
      "description": "Filter by team name (only when using a global API token).",
      "type": "string"
    },
    "page": {
      "description": "Page number for pagination (default 1).",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "per_page": {
      "description": "Results per page.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 250
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_on_call(team_name, page, per_page)

List on-call calendars/schedules and the users currently on call for escalation. Useful to see who gets paged. Uptime API: GET /api/v2/on-calls.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "team_name": {
      "description": "Filter by team name (only when using a global API token).",
      "type": "string"
    },
    "page": {
      "description": "Page number for pagination (default 1).",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "per_page": {
      "description": "Results per page.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 250
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_status_pages(team_name, page, per_page)

List public/private status pages with company name, subdomain, aggregate_state, and published flag. Uptime API: GET /api/v2/status-pages.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "team_name": {
      "description": "Filter by team name (only when using a global API token).",
      "type": "string"
    },
    "page": {
      "description": "Page number for pagination (default 1).",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "per_page": {
      "description": "Results per page.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 250
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡acknowledge_incident(incident_id, acknowledged_by)

Acknowledge an ongoing incident, signalling that someone is looking into it (stops further escalation). Idempotent-ish: acknowledging an already-acknowledged incident returns HTTP 409. Uptime API: POST /api/v3/incidents/{id}/acknowledge.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "incident_id": {
      "type": "string",
      "description": "The incident id to acknowledge (from list_incidents)."
    },
    "acknowledged_by": {
      "type": "string",
      "description": "User e-mail or a custom identifier of who is acknowledging the incident."
    }
  },
  "required": [
    "incident_id",
    "acknowledged_by"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡resolve_incident(incident_id, resolved_by)

Resolve an ongoing incident, marking it as handled/closed. Idempotent-ish: resolving an already-resolved incident returns HTTP 409. Uptime API: POST /api/v3/incidents/{id}/resolve.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "incident_id": {
      "type": "string",
      "description": "The incident id to resolve (from list_incidents)."
    },
    "resolved_by": {
      "type": "string",
      "description": "User e-mail or a custom identifier of who is resolving the incident."
    }
  },
  "required": [
    "incident_id",
    "resolved_by"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Empfohlene Prompts

retrieve_data
Get details about [item] from betterstack
Erwartete Tools: get_monitor
fetch_info
Fetch [information type] using betterstack
Erwartete Tools: get_monitor
list_items
List all [items] available in betterstack
Erwartete Tools: list_monitors
browse_collection
Show me the [collection] from betterstack
Erwartete Tools: list_monitors
explore_workflow
List available [items], then get details for each one using betterstack
Erwartete Tools: list_monitorsget_monitor

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet9 Tools