Token导航 LogoToken导航TokenDH.com
Have I Been Pwned MCP Server logo
安全风控stdio官方级别未说明来源级核验

Have I Been Pwned MCP Server

MCP Server

@smithery/cli

一个与Have I Been Pwned API集成的MCP服务器,用于检测账户或密码是否在数据泄露事件中暴露。

工具数

0

提示词数

0

GitHub Stars

2

资源数

0
数据安全JavaScriptClaudeClaude DesktopClaude

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

作者 / 组织

Cyreslab-AI

提供方

Cyreslab-AI

最后核验

2026/5/17 20:22

运行时

Node.js

快速接入

先看主来源和安装命令,再打开仓库或文档;下面只保留这个条目的关键接入事实。

命令预览

npx -y @smithery/cli install @Cyreslab-AI/hibp-mcp-server --client claude

详细介绍

我被MCP服务器供电了吗

](https://smithery.ai/server/@Cyreslab-AI/hibp-mcp-server)

一个模型上下文协议(MCP)服务器,提供与 我被人欺负了吗 API检查您的帐户或密码是否在数据泄露中被泄露。

特性

此MCP服务器提供四个主要工具:

  1. check_邮件:检查是否在数据泄露中发现了电子邮件地址
  2. check_password:检查密码是否在数据泄露中暴露(使用k-匿名)
  3. get_breach_details:获取有关特定数据泄露的详细信息
  4. list_all_breats:列出系统中的所有违规行为,可选择按域过滤

安装

通过Smithery安装

通过以下方式自动为Claude Desktop安装hibp-mcp服务器 史密瑟里:

npx -y @smithery/cli install @Cyreslab-AI/hibp-mcp-server --client claude

先决条件

设置

  1. 克隆此存储库:
   git clone https://github.com/Cyreslab-AI/hibp-mcp-server.git
   cd hibp-mcp-server
  1. 安装依赖项:
   npm install
  1. 构建服务器:
   npm run build
  1. 在MCP设置文件中配置服务器:

对于Claude VSCode扩展,请添加 ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json:

   {
     "mcpServers": {
       "hibp": {
         "command": "node",
         "args": ["/path/to/hibp-mcp-server/build/index.js"],
         "env": {
           "HIBP_API_KEY": "YOUR_API_KEY_HERE"
         },
         "disabled": false,
         "autoApprove": []
       }
     }
   }

对于Claude桌面应用程序,请添加到 ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)或其他平台上的类似路径。

使用示例

配置服务器后,您可以将其与Claude一起使用,以检查数据泄露情况:

检查电子邮件

User: Has my email address example@gmail.com been pwned?

Claude: Good news! This email address has not been found in any known data breaches.

或者,如果发现电子邮件存在违规行为:

User: Has my email address breached@example.com been pwned?

Claude: ⚠️ This email address was found in 3 data breaches.

Breach details:

1. Adobe (2013-10-04)
   Domain: adobe.com
   Description: In October 2013, 153 million Adobe accounts were breached...
   Compromised data: Email addresses, Password hints, Passwords, Usernames

2. LinkedIn (2012-05-05)
   Domain: linkedin.com
   Description: In May 2016, LinkedIn had 164 million email addresses and passwords exposed...
   Compromised data: Email addresses, Passwords

3. Dropbox (2012-07-01)
   Domain: dropbox.com
   Description: In mid-2012, Dropbox suffered a data breach which exposed...
   Compromised data: Email addresses, Passwords

Recommendations:
- Change your password for these services immediately
- If you used the same password elsewhere, change those too
- Enable two-factor authentication where available
- Consider using a password manager

检查密码

User: Has the password "password123" been exposed in any breaches?

Claude: ⚠️ This password has been exposed in data breaches 123,456 times!

Recommendations:
- Stop using this password immediately
- Change it on any site where you use it
- Use a unique, strong password for each account
- Consider using a password manager

获取违规详细信息

User: Tell me about the LinkedIn data breach

Claude: # LinkedIn Data Breach

**Date:** 2012-05-05
**Domain:** linkedin.com
**Accounts affected:** 164,611,595
**Verified:** Yes
**Data leaked:** Email addresses, Passwords

**Description:**
In May 2016, LinkedIn had 164 million email addresses and passwords exposed. Originally hacked in 2012, the data remained out of sight until being offered for sale on a dark market site 4 years later. The passwords in the breach were stored as SHA1 hashes without salt, the vast majority of which were quickly cracked in the days following the release of the data.

**Recommendations:**
- If you had an account on this service, change your password
- If you used the same password elsewhere, change those too
- Monitor your accounts for suspicious activity
- Be cautious of phishing attempts that may use this leaked information

列出所有违规行为

User: List all Adobe data breaches

Claude: Found 1 breaches for domain adobe.com:

1. Adobe (2013-10-04)
   Domain: adobe.com
   Accounts affected: 152,445,165
   Compromised data: Email addresses, Password hints, Passwords, Usernames

安全说明

  • 密码检查功能使用k匿名来检查密码,而无需将完整密码发送到Have I Been Pwned API
  • 只有密码的SHA-1哈希的前5个字符被发送到API
  • API返回与前缀匹配的哈希后缀列表,并在本地完成检查

API密钥配置

此服务器需要Have I Been Pwned API密钥才能运行大多数功能(密码检查除外)。您可以在获取API密钥 haveibeenpwned.com/API/关键.

API键应作为名为的环境变量提供 HIBP_API_KEY 在MCP设置配置中。

许可证

麻省理工学院

目录标签

目录标签

数据安全JavaScriptClaude本地部署密码检查账户安全数据泄露检测API集成

支持客户端

Claude DesktopClaude

接入字段

传输方式(transport,传输协议)

stdio

鉴权方式(authType,认证方式)

none

运行时(runtime,运行环境)

Node.js

部署方式(deploymentType,部署类型)

remote-capable

来源包(packageName,安装包名)

@smithery/cli

工具数量(toolCount,工具数)

0

资源数量(resourceCount,资源数)

0

提示词数量(promptCount,提示词数)

0

权限和风险

stdiononeremote-capable

接入前请确认传输方式、认证方式和部署位置,并根据实际工具能力限制访问范围。

安装前确认

不要直接授予不必要的文件、网络或账号权限;先核对安装命令和配置内容。

来源信息

继续浏览同类 MCP