Have I Been Pwned MCP Server

Created By
Cyreslab-AIa year ago
Overview

what is Have I Been Pwned MCP Server?

The Have I Been Pwned MCP Server is a Model Context Protocol server that integrates with the Have I Been Pwned API to help users check if their accounts or passwords have been compromised in data breaches.

how to use Have I Been Pwned MCP Server?

To use the server, install it via Smithery, configure it with your Have I Been Pwned API key, and then interact with it through commands to check emails or passwords for breaches.

key features of Have I Been Pwned MCP Server?

  • Check if an email address has been found in data breaches.
  • Check if a password has been exposed in data breaches using k-anonymity.
  • Get detailed information about specific data breaches.
  • List all breaches in the system, optionally filtered by domain.

use cases of Have I Been Pwned MCP Server?

  1. Verifying if an email address has been compromised in known data breaches.
  2. Checking the security of passwords against known breaches.
  3. Retrieving detailed information about specific data breaches for awareness and action.
  4. Monitoring breaches for specific domains to enhance security measures.

FAQ from Have I Been Pwned MCP Server?

  • Do I need an API key to use the server?

Yes, a Have I Been Pwned API key is required for most features.

  • How does the password checking feature work?

It uses k-anonymity to check passwords without sending the full password to the API, ensuring privacy.

  • Is the server secure?

Yes, it employs security measures to protect user data and privacy.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Cyreslab-AI
Star
0
Language
JavaScript
License
MIT license
Category
security

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago