Categories › Web & Browser › Web search engines & search APIs
Public post-incident reports as structured cases: search by symptom, read one, list by cause.
Remote server: your requests and data go to incidentlib-mcp.benchlet.com. Claude Code: claude mcp add --transport http incident-library https://incidentlib-mcp.benchlet.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
search_incidents — Use first, whenever someone describes a failure they are seeing. Pass the symptoms as a sentence or a few words, in English or Korean; returget_incident — Returns one case in full by its id: the structured write-up (symptoms, trigger, root cause, components, contributing factors, summary, impaclist_incidents — Lists cases by category, newest first, one page at a time: `count` and `cases` (id, title, organisation, date, root cause, page url), plus `get_topic — Returns one vocabulary value with every case that carries it and, under `related`, the other four kinds counted over those cases with case ivocab — Resolves words to vocabulary slugs for the filters of search_incidents, list_incidents and get_topic. With `query`, returns `matches`: the `Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.