Have I Been Pwned

Have I Been Pwned - Stealer Logs by Website Domain

hibp_get_stealer_logs_by_website_domain

Read-onlyIdempotent

Return email addresses historically observed in stealer logs for a website domain. Requires an OAuth-linked active subscription with the stealer-log feature; results do not establish current account access.

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 website domain to search for in stealer logs.
`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
`emails`	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.

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 signal read-only and idempotent behavior, so the description adds value by disclosing the OAuth-linked subscription requirement and importantly cautions that results do not establish current account access. This goes beyond the annotations and gives agents crucial interpretive context, though it stops short of covering other potential behaviors like rate limits or pagination quirks.

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 with no filler. The core purpose is front-loaded, and the subscription caveat is appended efficiently. Every sentence earns its place.

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?

The description covers the core purpose, the subscription prerequisite, and the key interpretive caveat. With an output schema present and fully documented parameters, nothing essential is missing for an agent to invoke the tool correctly. It is complete for its scope.

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 provides 100% coverage with descriptions for all four parameters, so the description does not need to add parameter-level detail. It adds no new semantic information about parameters, aligning with the baseline of 3 when schema coverage is high.

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 clearly states the verb 'Return' followed by the specific resource 'email addresses historically observed in stealer logs' and scopes it 'for a website domain.' The title and name further distinguish this from sibling tools that query by email or email domain, making the purpose unmistakable.

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 provides clear context that this tool searches by website domain and mentions the subscription requirement, which implies when it applies. However, it does not explicitly contrast with sibling tools (e.g., by email or by email domain) or state when not to use it, so it falls short of a perfect score.

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?