Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Incident Library

REMOTE · INCIDENTLIB-MCP.BENCHLET.COM

Public post-incident reports as structured cases: search by symptom, read one, list by cause.

+4 this week 78 Trust /100

Last scanned (15 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1539 tokens (~307/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +2
    • DNSSEC: fail → pass ▲ security
  • 15 Nov 26 0
    • Tool “search_incidents” rewrote its description, which is the text the model reads security
  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1
    • Tool “get_incident” rewrote its description, which is the text the model reads security
    • Tool “get_topic” rewrote its description, which is the text the model reads security
    • Tool “list_incidents” rewrote its description, which is the text the model reads security
    • Tool “vocab” rewrote its description, which is the text the model reads security
    • Schema quality: 213 → 298 ▼ functional
  • 11 Nov 26 +7
    • Authorization: unverified → partial ▲ security
    • Tool coverage: 93% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: good → excellent functional
    • “get_topic” reworded the description of “kind” cosmetic
    • “vocab” reworded the description of “limit” cosmetic
  • 10 Nov 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://incidentlib-mcp.benchlet.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=incidentlib-api.benchlet.com CN=YR2,O=Let's Encrypt,C=US 8 Nov 2026 6 Feb 2027 RSA 2048 SHA256-RSA 6251d79ba2d198d4836039977735bca2525
SANs: incidentlib-api.benchlet.com, incidentlib-mcp.benchlet.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of incidentlib-mcp.benchlet.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
benchlet.com. DS published 2371 13 Verified
incidentlib-mcp.benchlet.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://incidentlib-mcp.benchlet.com/mcp Verified 200
http (plaintext) http://incidentlib-mcp.benchlet.com/mcp HTTPS enforced 308 https://incidentlib-mcp.benchlet.com/mcp
MCP tools · 5 exposed · ~1,539 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_incident ~209

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.

NameTypeReqDescription
idstringyesCase id such as IL-0007
langstring–ko returns the Korean text of each field where the reviewers wrote one

No output schema declared.

No examples provided.

get_topic ~289

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.

NameTypeReqDescription
kindstringyesWhich category the slug belongs to
slugstringyesThe value's slug, e.g. capacity, coredns, pod-pending, no-alerting, github
symptomsstring–A symptom sentence that restricts the page to the cases it finds

No output schema declared.

No examples provided.

list_incidents ~344

Lists cases by category, newest first, one page at a time: `count` and `cases` (id, title, organisation, date, root cause, page url), plus `next_cursor` when more remain; call again with `cursor` for the following page. Use when the question names a category (a root cause, component, symptom, contributing factor, domain or organisation) rather than a symptom sentence; for a sentence use search_incidents, and for one category with its related categories counted use get_topic. Each filter is a slug (kebab-case) of its own kind: `symptom` is what was observed (pod-pending), `factor` is a condition that made it worse (no-alerting), `root_cause` is why it happened (capacity). Filters combine with AND. An unknown slug returns count 0 with no error; find the slug with vocab when you only have words. Reads only; the same filters return the same page.

NameTypeReqDescription
componentstring–e.g. coredns, vpc-cni
cursorstring–next_cursor from the previous page
domainstring–kubernetes or ai-infra
factorstring–contributing factor, e.g. no-alerting
langstring–ko returns the Korean text of each field where the reviewers wrote one
limitinteger–Cases per page
orgstring–the organisation's slug, e.g. github
root_causestring–e.g. capacity, config-change
symptomstring–e.g. pod-pending

No output schema declared.

No examples provided.

search_incidents ~492

Use first, whenever someone describes a failure they are seeing. Pass the symptoms as a sentence or a few words, in English or Korean; returns the reviewed public post-incident reports that answer it, best match first: the search ranks every case and keeps only those judged relevant to the sentence, usually a handful, and none when the library has no such incident (`total` 0). `total` is how many, `results` is one page of them in full (each with the case id, the page url and the source link), `matched` is every one as a row, and `next_cursor` fetches the next page. `interpreted` lists the values the sentence named (the search moves cases carrying them up) and any organisation it named (a filter to choose, not a ranking signal); `facets` count the results by root cause, component, symptom, contributing factor and organisation with the case ids, which answers 'what usually caused this' from the same call. The optional slug filters keep only cases carrying those values (AND); take slugs from facets, interpreted or vocab. Follow with get_incident for the full case.

NameTypeReqDescription
componentstring–Keep only cases with this component slug, e.g. coredns
cursorstring–next_cursor from the previous page
domainstring–Keep only cases in this domain, e.g. kubernetes or ai-infra
factorstring–Keep only cases with this contributing factor slug, e.g. no-alerting
langstring–ko returns the Korean text of each field where the reviewers wrote one
limitinteger–Cases per page
orgstring–Keep only cases of this organisation, by slug, e.g. github (from facets.orgs, interpreted or vocab)
root_causestring–Keep only cases with this root cause slug, e.g. capacity
symptomstring–Keep only cases with this symptom slug, e.g. pod-pending
symptomsstring–What is observed, as a sentence or a few words, e.g. 'pods cannot get an IP, nodes show no available addresses' or 'coredns oom'. Leave it out to list every case under the slug filters, newest first;…

No output schema declared.

No examples provided.

vocab ~205

Resolves words to vocabulary slugs for the filters of search_incidents, list_incidents and get_topic. With `query`, returns `matches`: the `limit` values nearest in meaning to the words, nearest first, each with kind, slug, English and Korean name and page url (e.g. 'cert ran out' finds certificate-expiry); `kind` restricts to one category. There is no similarity cutoff: the list is always `limit` long, so when the words name nothing in the library the matches are far from them; read the names before using a slug, and when none fits, search with search_incidents instead of filtering. Without `query`, returns every value of every kind with names, aliases and definitions (a large answer; prefer `query`). Reads only.

NameTypeReqDescription
kindstring–Only this kind
limitinteger–Values to return
querystring–A few words naming what you are looking for

No output schema declared.

No examples provided.

Install

How do I install the Incident Library MCP server?

Incident Library is a hosted endpoint at https://incidentlib-mcp.benchlet.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · incidentlib-mcp.benchlet.com

# add to Claude Code
claude mcp add --transport http com-benchlet-incidentlib 'https://incidentlib-mcp.benchlet.com/mcp'
Common questions

What is the Incident Library MCP server?

Incident Library is an MCP server listed in the public MCP registry as com.benchlet/incidentlib. Public post-incident reports as structured cases: search by symptom, read one, list by cause. This page covers its hosted endpoint (https://incidentlib-mcp.benchlet.com/mcp).

Is the Incident Library MCP server safe to use?

Incident Library scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Incident Library MCP server expose?

Incident Library exposes 5 tools: search_incidents, get_incident, list_incidents, get_topic, vocab. Their descriptions and schemas cost roughly 1,539 tokens of context every time the server is loaded.

Does the Incident Library MCP server require authentication?

No. We connected to Incident Library without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Incident Library MCP server still maintained?

Incident Library is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Incident Library MCP server?

VerifyMCP ran 13 checks on Incident Library, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.