# Hibp (npm · @pipeworx/mcp-hibp)

Have I Been Pwned MCP

- Trust score: 86/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-07

## Components

- remote · `gateway.pipeworx.io`: 87/100, [markdown](https://verifymcp.io/servers/pipeworx-io-hibp/hibp-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-hibp/hibp-mcp)
- npm · `@pipeworx/mcp-hibp`: 86/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-hibp/pipeworx-mcp-hibp.md), [page](https://verifymcp.io/servers/pipeworx-io-hibp/pipeworx-mcp-hibp)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-hibp`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-07.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-hibp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 475 tokens (~79/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Hibp MCP server?

Hibp runs locally as an npm package, launched with npx -y @pipeworx/mcp-hibp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-hibp -- npx -y @pipeworx/mcp-hibp
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-hibp": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-hibp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-hibp": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-hibp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-hibp -- npx -y @pipeworx/mcp-hibp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-hibp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-hibp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-hibp --command npx --arg -y --arg @pipeworx/mcp-hibp
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-hibp:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-hibp"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-hibp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-hibp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-hibp -t stdio -c npx -a -y @pipeworx/mcp-hibp
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-hibp": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-hibp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 84, +26)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-02 (score 58, −24)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 82, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 82)

First indexed and scored.

## MCP tools (6)

### `check_password` (~89 tokens)

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.

Input parameters:

- `password` (string, required): Password to check (stays inside the worker)

### `check_password_prefix` (~74 tokens)

Direct k-anonymity lookup: pass the first 5 hex chars of a SHA-1 password hash, get back all SHA-1 suffixes with their pwned counts. Use this if you're hashing client-side and only want to send the prefix.

Input parameters:

- `sha1_prefix` (string, required): 5 hexadecimal characters

### `list_breaches` (~76 tokens)

List all publicly-known data breaches catalogued by HIBP. Optionally filter to a specific domain (e.g., "linkedin.com"). Returns name, title, breach date, added date, affected accounts, description, data classes exposed, and verification status.

Input parameters:

- `domain` (string): Restrict to a specific breached domain

### `get_breach` (~55 tokens)

Fetch a single breach by name (the "Name" field from list_breaches, e.g., "Adobe", "LinkedIn"). Returns full breach metadata.

Input parameters:

- `name` (string, required): Breach name (case-sensitive)

### `list_data_classes` (~42 tokens)

Canonical list of HIBP "data class" tags (e.g., "Email addresses", "Passwords", "Geographic locations"). Useful for filtering breaches.

### `check_account` (~86 tokens)

Look up breaches an email account has been seen in. REQUIRES a paid HIBP subscription key (pass _apiKey). Returns the set of breach names; combine with get_breach for details.

Input parameters:

- `account` (string, required): Email address
- `truncate` (boolean): Return only breach names (default true). Set false for full breach objects (counts as 1 query).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-hibp/pipeworx-mcp-hibp#diagnostics

## Score history

- 2026-11-07: 86
- 2026-11-06: 86
- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 58
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 82

## Common questions

### What is the Hibp MCP server?

Hibp is an MCP server listed in the public MCP registry as io.github.pipeworx-io/hibp. Have I Been Pwned MCP. This page covers its npm package (@pipeworx/mcp-hibp).

### Is the Hibp MCP server safe to use?

Hibp scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Hibp MCP server expose?

Hibp exposes 6 tools: check_password, check_password_prefix, list_breaches, get_breach, list_data_classes, check_account. Their descriptions and schemas cost roughly 422 tokens of context every time the server is loaded.

### Is the Hibp MCP server still maintained?

Hibp is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Hibp MCP server under?

Hibp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Hibp MCP server?

VerifyMCP ran 16 checks on Hibp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-hibp
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-hibp
- Repository: https://github.com/pipeworx-io/mcp-hibp
- Website: https://pipeworx.io/packs/hibp
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-hibp/pipeworx-mcp-hibp.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-hibp/pipeworx-mcp-hibp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-hibp/pipeworx-mcp-hibp.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-hibp/pipeworx-mcp-hibp