all tools / incident
As of the latest check, Glimind tracks 17 incident AI agent (MCP) tools, of which 5 are healthy right now. The table below ranks them live-first by real-time reliability.
| tool | status | what it does | |
|---|---|---|---|
| acknowledge_incident dev.uptimepage/uptimepage | healthy | Acknowledge an incident: take ownership and halt escalation. Internal/operational only — does NOT post anything to the public status page. U | alternatives |
| unpublish_incident dev.uptimepage/uptimepage | healthy | Hide a published incident from the public status pages again. Its operator timeline is untouched. Asks for confirmation where the client can | alternatives |
| publish_incident dev.uptimepage/uptimepage | healthy | Publish an incident so it appears on every status page carrying the affected monitor, optionally seeding the public title and description. A | alternatives |
| resolve_incident dev.uptimepage/uptimepage | healthy | Resolve an incident (mark the operational state resolved). Internal only — does not post to the public status page. Asks for confirmation wh | alternatives |
| post_incident_update dev.uptimepage/uptimepage | healthy | Post a public, customer-facing update to an incident's status-page timeline (phase + message). This is what your subscribers and status-page | alternatives |
| resolve_incident io.usefulapi/betterstack | auth | Resolve an ongoing incident, marking it as handled/closed. Idempotent-ish: resolving an already-resolved incident returns HTTP 409. Uptime A | alternatives |
| resolve_incident io.github.PagerDuty/pagerduty-mcp | unknown | Resolve a PagerDuty incident | alternatives |
| get_incident io.github.PagerDuty/pagerduty-mcp | unknown | Get details of a specific PagerDuty incident | alternatives |
| acknowledge_incident io.github.PagerDuty/pagerduty-mcp | unknown | Acknowledge a PagerDuty incident | alternatives |
| rootly_incidents_list io.github.WYRE-AI/rootly-mcp | unknown | List incidents with optional status/severity filters | alternatives |
| rootly_incidents_get io.github.WYRE-AI/rootly-mcp | unknown | Get a single incident by ID | alternatives |
| rootly_incidents_update io.github.WYRE-AI/rootly-mcp | unknown | Update title, summary, status, or severity | alternatives |
| rootly_alerts_acknowledge io.github.WYRE-AI/rootly-mcp | unknown | Acknowledge an alert | alternatives |
| rootly_alerts_resolve io.github.WYRE-AI/rootly-mcp | unknown | Resolve an alert | alternatives |
| rootly_alerts_update io.github.WYRE-AI/rootly-mcp | unknown | Update alert status or summary | alternatives |
| rootly_incidents_create io.github.WYRE-AI/rootly-mcp | unknown | Create a new incident | alternatives |
| rootly_alerts_create io.github.WYRE-AI/rootly-mcp | unknown | Create a new alert | alternatives |
As of the latest check, Glimind tracks 17 incident AI agent (MCP) tools, of which 5 are healthy right now. The table below ranks them live-first by real-time reliability. Glimind rates each neutrally (0–100) from safe liveness probes plus privacy-clean real-usage outcomes — see each tool's live page for its current score and a working alternative if it's down.
Ranked live-first by current verdict (healthy → degraded → down), then by the neutral reliability score. Glimind sells no tools, so the ranking is unconflicted.
Every tool here links to its live alternatives — capability-matched substitutes that are healthy now. Or query https://glimind.com/v1/alternatives/{toolId}.
Live data via MCP/REST. Neutral ratings — Glimind only measures.