Hibp

List Breaches

list_breaches

Read-onlyIdempotent

List all publicly-known data breaches catalogued by HIBP. Optionally filter to a specific domain (e.g., "linkedin.com"). Returns name, title, breach date, added date, affected accounts, description, data classes exposed, and verification status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	No	Restrict to a specific breached domain

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes	Number of breaches returned
`breaches`	Yes	List of breach records

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {},
+  {
+    "domain": "linkedin.com"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "breaches": {
+      "description": "List of breach records",
+      "items": {
+        "properties": {
+          "added_date": {
+            "description": "Date added to HIBP",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "breach_date": {
+            "description": "Date breach occurred",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "data_classes": {
+            "description": "Types of data exposed",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "description": {
+            "description": "Detailed breach description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "domain": {
+            "description": "Primary domain affected",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "is_fabricated": {
+            "description": "Whether breach is fabricated",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "is_malware": {
+            "description": "Whether malware was involved",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "is_retired": {
+            "description": "Whether breach is retired",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "is_sensitive": {
+            "description": "Whether breach is sensitive",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "is_spam_list": {
+            "description": "Whether this is a spam list",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "is_verified": {
+            "description": "Whether breach is verified",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "logo_path": {
+            "description": "Path to breach logo image",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "modified_date": {
+            "description": "Last modification date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Unique breach name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "pwn_count": {
+            "description": "Number of affected accounts",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Human-readable breach title",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "name",
+          "title",
+          "domain",
+          "breach_date",
+          "added_date",
+          "modified_date",
+          "pwn_count",
+          "description",
+          "data_classes",
+          "is_verified",
+          "is_fabricated",
+          "is_sensitive",
+          "is_retired",
+          "is_spam_list",
+          "is_malware",
+          "logo_path"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of breaches returned",
+      "type": "number"
+    }
+  },
+  "required": [
+    "count",
+    "breaches"
+  ],
+  "type": "object"
+}

First observedMay 11, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. Description adds that it's an HIBP catalog and lists return fields, but no additional behavioral traits like rate limits or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, efficient and front-loaded. Could be slightly more structured (e.g., bullet points for return fields), but overall concise and informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given low complexity (single optional parameter) and existence of output schema, description fully covers what the tool does, including return fields. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 1 parameter with description 'Restrict to a specific breached domain'. Description also mentions domain filter. Schema coverage is 100%, so description adds minimal extra meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it lists all publicly-known data breaches from HIBP, with optional domain filtering. It distinguishes from siblings like get_breach (single breach) and check_account.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States optional domain filter but does not explicitly specify when to use this tool vs alternatives like get_breach or list_data_classes. Usage context is implied but lacks direct guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hibp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.