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
ParameterTypeShareRequiredUsual description
idstring62.5%100%Case id such as IL-0007
incidentIdstring25%100%The incident id, as reported by list_incidents.
incident_idnumber12.5%100%Numeric AIID incident id
langstring12.5%0%ko returns the Korean text of each field where the reviewers wrote one
projectIdstring12.5%100%—
selectarray12.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★Live
1OneUptimeoneuptime · Cloud & DevOps7.8kyes
2Uptimepageuptimepage · Cloud & DevOps61yes
3Loadsterloadster · Testing & QA—yes
4Incident Libraryteam-dogfoot · Cloud & DevOps—yes
5NEARpediaunitynodes · Documents & Knowledge—yes
6Ai Incident Dbpipeworx-io · Cloud & DevOps—yes
7Faultlinefltln-io · Cloud & DevOps—yes
8CollectSEAkelvin-ling · Security & Identity—yes

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.