Skip to main content
Glama

check_password_breach

Check if a password has been exposed in data breaches using anonymized hash lookup. Use to validate new passwords or flag compromised credentials.

Instructions

Check if a password has appeared in known data breaches.

Uses the k-anonymity method: only the first 5 characters of the SHA-1 hash
of the password are ever sent over the network. The API returns a list of
matching hash suffixes which are compared locally — the full password and
hash are never transmitted. Data sourced from HaveIBeenPwned and similar
breach databases.

Use this to validate new passwords at registration or to prompt users
to change a compromised credential. Safe to call with real passwords due
to the k-anonymity design.

Args:
    password: The password string to check. Transmitted as a partial hash
              (first 5 chars of SHA-1 only) — never the plaintext password.

Returns:
    breached (bool): True if the password appears in breach databases.
    count: Number of times this password has been seen in breaches.
           A count > 0 means the password should not be used.
           A count of 0 means it has not been seen (not a guarantee of safety).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordYes
Behavior5/5

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

No annotations provided, so description carries full burden. Detailed explanation of k-anonymity method (only first 5 chars of SHA-1 hash sent), local comparison, and that full password never transmitted. Discloses data source (HaveIBeenPwned etc.).

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?

Well-structured with paragraphs for purpose, method, usage, and returns. Some redundancy could be trimmed (e.g., 'the full password and hash are never transmitted' appears twice), but still efficient and clear.

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?

Comprehensive for a sensitive security tool. Explains method, return values (breached bool and count), interpretation of count, and limitations (not a guarantee of safety). No output schema, so description covers returns adequately.

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

Parameters5/5

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

Schema has 0% coverage for parameter descriptions. The description adds essential meaning: password is transmitted as partial hash only, never plaintext. Explains the security mechanism for the single 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?

Clearly states 'check if a password has appeared in known data breaches' with specific verb and resource. Distinguishes from sibling tools like validate_email, dns_lookup, etc., which are unrelated.

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

Usage Guidelines5/5

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

Explicitly advises use cases: 'validate new passwords at registration or prompt users to change a compromised credential.' Also implies safety due to k-anonymity, guiding appropriate use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ForeverTools/kiprio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server