Token导航 LogoToken导航TokenDH.com
研究检索敏感数据clawhub未标认证来源可访问clear审计提醒

toolweb-breached-email-checktoolweb 违反了电子邮件检查

Agent Skill

toolweb-breached-email-check 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

6,586

周安装

280

GitHub Stars

公开资料未说明

下载量

2,307
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:toolweb-breached-email-check(toolweb 违反了电子邮件检查)
来源仓库:https://github.com/krishnakumarmahadevan-cmd/toolweb-breached-email-check
安装命令:
openclaw skills install toolweb-breached-email-check
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install toolweb-breached-email-check

简介

检查电子邮件是否出现在已知的数据泄露事件中,并获取详细的泄露历史记录、严重程度、受损数据和补救建议。

SKILL.md

Breached Email Check

Check whether an email address has appeared in known data breaches. Submit any email address and get back a breach history report — including which breaches exposed the address, what data types were compromised, breach dates, and remediation recommendations. Essential for user onboarding security checks, employee credential monitoring, and threat exposure assessments.


Usage

{
  "tool": "breached_email_check",
  "input": {
    "email": "user@example.com"
  }
}

Parameters

FieldTypeRequiredDescription
emailstringThe email address to check against known data breach databases

What You Get

  • Breach status — whether the email has been found in any known breaches
  • Breach list — names of breaches the email appeared in, with dates
  • Compromised data types — what was exposed per breach (passwords, phone numbers, physical addresses, credit cards, etc.)
  • Breach severity rating — overall risk level based on sensitivity of exposed data
  • Paste exposure — whether the email has appeared in public paste sites (Pastebin, etc.)
  • Remediation guidance — specific actions to take based on breach findings (password reset, MFA, account monitoring)

Example Output

{
  "email": "user@example.com",
  "breached": true,
  "breach_count": 3,
  "severity": "High",
  "breaches": [
    {
      "name": "LinkedIn (2012)",
      "date": "2012-06-05",
      "compromised_data": ["Email Addresses", "Passwords"],
      "description": "Password hashes exposed in large-scale breach; later cracked and published",
      "verified": true
    },
    {
      "name": "Adobe (2013)",
      "date": "2013-10-04",
      "compromised_data": ["Email Addresses", "Password Hints", "Passwords", "Usernames"],
      "description": "Source code and encrypted credentials exposed for 153 million accounts",
      "verified": true
    },
    {
      "name": "DataBreach.com (2020)",
      "date": "2020-03-21",
      "compromised_data": ["Email Addresses", "Phone Numbers", "Physical Addresses"],
      "description": "Aggregated breach data compilation including PII from multiple sources",
      "verified": false
    }
  ],
  "paste_exposure": true,
  "paste_count": 1,
  "remediation": [
    "Change passwords on all accounts using this email address immediately",
    "Enable multi-factor authentication (MFA) on all associated accounts",
    "Check for unauthorized account activity on LinkedIn and Adobe",
    "Consider using a unique email alias for sensitive accounts going forward",
    "Monitor credit report if physical address was exposed"
  ]
}

When email is clean

{
  "email": "safe@example.com",
  "breached": false,
  "breach_count": 0,
  "severity": "None",
  "breaches": [],
  "paste_exposure": false,
  "paste_count": 0,
  "remediation": [
    "No known breaches found — continue using strong, unique passwords",
    "Enable MFA as a proactive measure"
  ]
}

Use Cases

  • User onboarding — check if a new user's email is in known breaches at signup
  • Employee security audits — identify staff with exposed credentials before they become an attack vector
  • Threat exposure assessment — assess corporate email domain exposure across your workforce
  • Password reset triggers — automatically prompt users with breached emails to reset credentials
  • Security awareness — show users their personal breach history to drive MFA adoption

API Reference

Base URL: https://portal.toolweb.in/apis/security/breached-email-check

EndpointMethodDescription
/check-breachPOSTCheck an email address against known data breach databases

Authentication: Pass your API key as X-API-Key header or mcp_api_key argument via MCP.


Pricing

PlanDaily LimitMonthly LimitPrice
Free5 / day50 / month$0
Developer20 / day500 / month$39
Professional200 / day5,000 / month$99
Enterprise100,000 / day1,000,000 / month$299

About

ToolWeb.in — 200+ security APIs, CISSP & CISM certified, built for enterprise security practitioners.

Platforms: Pay-per-run · API Gateway · MCP Server · OpenClaw · RapidAPI · YouTube

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

95.24%
按下载量换算2,197

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills