MCP tool reference · #484 of 563 by publishers
get_incident
Exposed by 8 servers from 8 publishers, read from the live servers by the Serverdex check; most of them sit in Cloud & DevOps; 62.5% of them take a id parameter; the most-starred is OneUptime (7.8k stars).
get_incident(id: string, incidentId: string, …)Parameters
share = % of the 8 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| id | string | 62.5% | 100% | Case id such as IL-0007 |
| incidentId | string | 25% | 100% | The incident id, as reported by list_incidents. |
| incident_id | number | 12.5% | 100% | Numeric AIID incident id |
| lang | string | 12.5% | 0% | ko returns the Korean text of each field where the reviewers wrote one |
| projectId | string | 12.5% | 100% | — |
| select | array | 12.5% | 0% | Omit for all but subscriberNotificationStatusMessage, subscriberNotificationStatusMessageOnPostmortemPublished, customFields, createdStateLog, seriesLabels, mon |
Source: the input schema each server returns for get_incident, aggregated over the 8 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with get_incident
8 of 8 · 8 publishers · 8 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes get_incident |
|---|---|---|---|---|---|---|
| 1 | OneUptimeoneuptime · Cloud & DevOps | oneuptime | Cloud & DevOps | 7.8k | yes | Get one Incident by ID. |
| 2 | Uptimepageuptimepage · Cloud & DevOps | uptimepage | Cloud & DevOps | 61 | yes | One incident: affected monitor, what opened it, severity, open/resolved times, error sample, the full operator-update timeline, and the status pages an incident with no monitor is posted to. For an incident another tool's alert opened, also the source and what the tool sent: labels, annotations, links and the worst severity it reported. Read-only. |
| 3 | Loadsterloadster · Testing & QA | loadster | Testing & QA | — | yes | Get a single Incident: when it opened and closed, every notification that went out with its delivery outcome, the status events recorded on it, and the ids of the Cycles that opened and closed it. To reconstruct what happened, read those Cycles with get_monitor_cycle_detail, and cross-read the Monitor's configuration and its Script so the diagnosis names the concrete step, URL, or threshold at fau |
| 4 | Incident Libraryteam-dogfoot · Cloud & DevOps | team-dogfoot | Cloud & DevOps | — | yes | Returns one case in full by its id: the structured write-up (symptoms, trigger, root cause, components, contributing factors, summary, impact, timeline, detection, remediation, action items, lessons), its sources with archived copies, and `similar_cases`. Use after search_incidents, list_incidents or get_topic has given you a case id; not for finding cases (use search_incidents for symptoms, list_ |
| 5 | NEARpediaunitynodes · Documents & Knowledge | unitynodes | Documents & Knowledge | — | yes | One NEAR ecosystem security incident in full, with DefiLlama's description, by the id list_incidents prints (e.g. "llama-1546-2026-04-16"). |
| 6 | Ai Incident Dbpipeworx-io · Cloud & DevOps | pipeworx-io | Cloud & DevOps | — | yes | Fetch a full AI Incident Database record by numeric incident_id from the stored snapshot copy; returns title, date, description, alleged deployer/developer/harmed parties, and all linked report titles, domains, URLs and dates. Report text, authors and submitters are not included. |
| 7 | Faultlinefltln-io · Cloud & DevOps | fltln-io | Cloud & DevOps | — | yes | Get an incident's full record: timeline of every update, escalations, runbook results, AI summary, and post-mortem if drafted. Call this before acting on an incident. |
| 8 | CollectSEAkelvin-ling · Security & Identity | kelvin-ling | Security & Identity | — | yes | Full record for one incident by ID (e.g. SEA-POST-005): what happened, source, failure pattern, safeguards and review status. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.