Incident Library
v1.0.1Public post-incident reports as structured cases: search by symptom, read one, list by cause.
Endpoint health
online- Last checked
- 11/20/2026, 7:16:35 AM
- Latency
- 634 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.benchlet%2Fincidentlib
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.benchlet/incidentlib": {
"url": "https://incidentlib-mcp.benchlet.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
5 shown · authentication unknown
Get one incident
get_incident
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_incidents or get_topic for a category). `lang: ko` returns the Korean text of each field where the reviewers wrote one, otherwise English. The id must look like IL-0007; an id of that shape that matches no approved case returns an error result saying so, and an id of another shape is rejected before the call. Every call for the same id returns the same case.
Schema valid · SHA-256 33d05a9cffcd…
View input schema
{ "type": "object", "properties": { "id": { "type": "string", "pattern": "^IL-\\d+$", "description": "Case id such as IL-0007" }, "lang": { "default": "en", "description": "ko returns the Korean text of each field where the reviewers wrote one", "type": "string", "enum": [ "en", "ko" ] } }, "required": [ "id" ], "$schema": "http://json-schema.org/draft-07/schema#" }Get a root cause, component, symptom, contributing factor or organisation
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 ids: for a symptom, the root causes behind it (answers 'what usually causes this'); for a root cause, the components and factors seen with it. Use when you already have a slug and want the picture around it; use vocab to find the slug from words, list_incidents for a plain paged list, search_incidents for a symptom sentence. `kind` is the slug's category: root_causes, components, symptoms, factors or orgs (the organisations that published cases). With `symptoms`, the page keeps only the cases that sentence finds, best match first, and `query` echoes it, so 'certificate expiry, but only where DNS was involved' is one call. The answer is not paged: `count` and `cases` hold every case of the value (at most a few dozen today). An unknown slug or a slug of the wrong kind returns an error result naming it; nothing is written.
Connections
streamable-http
https://incidentlib-mcp.benchlet.com/mcp