Have I Been Pwned

Have I Been Pwned - Subscribed Domains

hibp_list_subscribed_domains

Read-onlyIdempotent

List the domains associated with the authenticated HIBP subscription.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of items to include in the response. Defaults to 25.
`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
`offset`	No
`hasMore`	No
`message`	No	Present when the tool returns an error.
`guidance`	No	Additional guidance for resolving the tool error.
`nextOffset`	No
`statusCode`	No	Present when the tool returns an error.
`totalCount`	No
`returnedCount`	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.
`subscribedDomains`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 2, 2026
- removedOutput schema / properties / subscribedDomains / items / properties / NextSubscriptionRenewal / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / subscribedDomains / items / properties / NextSubscriptionRenewal / type
```
Added value: +[
+  "string",
+  "null"
+]
```

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds only the authenticated-subscription scope and does not disclose auth mechanics, rate limits, or pagination behavior. This is consistent with the annotations, so there is no contradiction.

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?

The description is a single front-loaded sentence with no filler or repeated title boilerplate. Every word contributes to identifying both the operation and the data scope.

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

Completeness4/5

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

For a read-only listing tool with zero required parameters, complete schema coverage, and an output schema, the brief purpose statement is largely sufficient. The only minor gap is that it does not explicitly mention API-key requirements or rate limits, though the word 'authenticated' hints at the former.

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?

Schema description coverage is 100%, and the schema already documents limit, offset, and response_format including defaults, bounds, and behavior. The description adds no additional parameter-level meaning, so the baseline 3 applies.

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

Purpose4/5

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

The description uses a specific verb ('List') and names a clear resource ('the domains associated with the authenticated HIBP subscription'), so an agent can tell what this tool returns. It does not explicitly contrast itself with siblings such as hibp_get_subscription_status, but the domain-scoped wording is sufficiently distinct.

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?

The description implies this is the tool to use when an agent needs the domains tied to the authenticated HIBP subscription, but it does not explicitly state when to choose it over alternatives. There are no exclusions or sibling routing cues, such as pointing to hibp_get_subscription_status for subscription metadata.

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?