Skip to main content
Glama

Hibp Check Password

hibp_check_password
Read-onlyIdempotent

Check whether a password appears in known breach corpora. Uses k-anonymity: the password is SHA-1ed locally, only the first 5 hex chars leave the worker, and the response is filtered to match the rest. Returns pwned count (0 = not seen). The password itself is never transmitted.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "password": "correct-horse-battery-staple"
    },
    "name": "hibp_check_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYesPassword to check (stays inside the worker)

Output Schema

NameRequiredDescriptionDefault
pwnedYesWhether password appears in breach corpus
adviceYesSecurity advice based on pwned status
pwned_countYesNumber of times password seen in breaches
sha1_prefixYesFirst 5 hex characters of SHA-1 hash

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses real behavioral traits: local SHA-1 hashing, only the 5-character prefix leaving the worker, client-side response filtering, and a pwned count where 0 means not seen. It also states plainly that the password is never transmitted, which matters for a privacy-sensitive call.

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?

Four short sentences, front-loaded with the purpose, then the mechanism, then the return value. The final sentence ('The password itself is never transmitted') repeats the earlier statement that only 5 hex characters leave the worker, so one idea appears twice.

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?

An output schema exists, so return format does not need explaining, but the description still names the pwned count and the 0 = not seen convention. It covers what an agent needs for this one-parameter read-only tool; only operational concerns such as rate limiting or error behavior are absent.

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

Parameters4/5

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

Schema coverage is 100% and there is only one parameter, so the baseline is 3. The description adds meaning beyond the schema by emphasizing that the password never leaves the worker and is hashed locally, but this largely restates the schema note that the password 'stays inside the worker'.

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 gives a specific verb and resource: 'Check whether a password appears in known breach corpora.' The k-anonymity explanation also implicitly distinguishes it from check_password_prefix, but it never names that sibling explicitly, so an agent must infer the split between the two tools.

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?

Usage is only implied: the description makes clear this tool checks a password end to end, but it does not state when to prefer it over check_password_prefix or when it should not be used (for example, bulk checking or offline use). No exclusions or prerequisite guidance is given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.