Have I Been Pwned

Have I Been Pwned - Stealer Logs by Email

hibp_get_stealer_logs_by_email

Read-onlyIdempotent

Return website domains historically observed in stealer logs for an email address. 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
`email`	Yes	The email address to search for in stealer logs.
`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
`email`	No
`limit`	No
`offset`	No
`domains`	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.5/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds important behavioral context: the requirement for an OAuth-linked active subscription with the stealer-log feature, and the differentiation that results are historical and do not establish current account access. This is especially valuable for avoiding misinterpretation of the data.

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 two tightly written sentences with no filler. The core action and resource are front-loaded in the first sentence, and the follow-up sentence carries essential caveats about subscription requirements and data interpretation.

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 the annotations, full schema coverage, and existing output schema, the description provides everything an agent needs to correctly select and invoke the tool: the resource returned, the required auth context, a key interpretation caveat, and enough scope to distinguish it from related siblings.

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 already documents all four parameters with full coverage, so the description need not repeat parameter details. The description reinforces the semantic distinction that the primary input is an email address, not a domain, but it does not add meaning beyond the schema's existing parameter descriptions.

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 states a specific verb ('Return') and resource ('website domains historically observed in stealer logs') for a specific input ('an email address'), clearly distinguishing this tool from the sibling stealer-log tools that operate on email domains or website domains. It conveys exactly what the tool does in one sentence.

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 is for lookup by a full email address, which implicitly differentiates it from the sibling tools by_email_domain and by_website_domain. It also notes a prerequisite (OAuth-linked active subscription with the stealer-log feature), but it does not explicitly name alternatives or state when to choose a sibling tool instead.

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?