Have I Been Pwned

Have I Been Pwned - Breached Domain

hibp_get_breached_domain

Read-onlyIdempotent

Return breached aliases for a verified domain. This tool requires an authorized subscription via OAuth bearer token.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of items to include in the response. Defaults to 25.
`domain`	Yes	The verified domain to search.
`offset`	No	Number of items to skip before returning results. Defaults to 0.
`response_format`	No	Format only the text content as markdown (default) or a JSON string. The same machine-readable data is always returned in structuredContent.	markdown

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`domain`	No
`offset`	No
`hasMore`	No
`message`	No	Present when the tool returns an error.
`guidance`	No	Additional guidance for resolving the tool error.
`aliasCount`	No
`nextOffset`	No
`statusCode`	No	Present when the tool returns an error.
`totalCount`	No
`returnedCount`	No
`breachesByAlias`	No
`rateLimitResetAt`	No	UTC timestamp indicating when the current rate limit window should have reset.
`retryAfterHeaders`	No	Retry headers that mirror the standard HTTP rate-limit response when applicable.
`retryAfterSeconds`	No	How long to wait before retrying, when the tool is rate limited.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / response_format / description

Previous value: -"Format the text response as markdown (default) or JSON. structuredContent is always returned."New value: +"Format only the text content as markdown (default) or a JSON string. The same machine-readable data is always returned in structuredContent."

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedJul 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to repeat safety traits. It adds useful behavioral context by stating the OAuth/subscription requirement and the verified-domain prerequisite, which are not visible in the annotations.

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

Conciseness5/5

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

Two sentences, no filler, with the core purpose front-loaded and the key requirement immediately after. Every sentence adds information.

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 that an output schema exists, annotations cover safety, and the four parameters are fully documented in the schema, the description supplies the missing context: what the tool returns and the access requirement. Nothing essential is missing for an agent to select and invoke it correctly.

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?

The input schema has 100% parameter coverage, so the baseline is 3. The description does not materially expand on parameter meaning beyond what the schema already states, such as 'verified domain to search' for the domain parameter.

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?

The description opens with a specific verb and resource: 'Return breached aliases for a verified domain.' This clearly distinguishes the tool from sibling tools like hibp_get_breached_account and hibp_get_breached_account_range by focusing on domain-level aliases.

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

Usage Guidelines4/5

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

The description conveys clear usage context by requiring both a verified domain and an authorized subscription via OAuth bearer token. It does not explicitly name alternatives or exclusion conditions, but the prerequisites are stated directly.

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

All Have I Been Pwned 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.

Resources

Need Help?