LeakData

Check breach exposure for your verified email and check locally computed password hash prefixes.

我該用這個嗎

品質與安全性

A
說明品質
100%
結構描述完整度
95%
命名品質
50%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

發現項目(2)

  • LOWTool 'leakdata.search' doesn't follow camelCase/snake_case在 leakdata.search 中
  • LOWTool 'leakdata.password_prefix_check' doesn't follow camelCase/snake_case在 leakdata.password_prefix_check 中

根據工具定義與協定合規性的自動化分析。

上下文成本

~802Token(工具定義)
~2.8 KB典型回應大小
中等的注意力影響(128k 上下文的 0.63%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "leakdata-mcp": {
      "url": "https://leakdata.io/mcp"
    }
  }
}

遠端端點

https://leakdata.io/mcpstreamable-http

它能做什麼

工具清單

工具(2)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢leakdata.search(type, query)

Use this when the linked LeakData user asks to check their verified primary email. For a current check, call this tool and report only its returned results. Never present earlier conversation results as a new check; if the call fails, say the check could not be completed. For their own email without an address, set type to email and omit query: the server resolves the verified primary email from the linked account. If the user supplies an email address, preserve it in query for ownership validation. Never guess an email address or recover it from earlier conversations when query can be omitted. Domain checks are not available through this app; explain this without calling a tool. Arbitrary third-party identifiers, usernames, phone numbers, raw leak records, and credentials are not returned.

輸入結構描述

{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "enum": [
        "email"
      ]
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 320,
      "description": "Omit for the linked account's verified primary email. If an email is supplied, it must match that verified primary email."
    }
  },
  "required": [
    "type"
  ],
  "additionalProperties": false
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "found": {
      "type": "boolean"
    },
    "breachCount": {
      "type": "integer",
      "minimum": 0
    },
    "type": {
      "type": "string",
      "enum": [
        "email"
      ]
    },
    "breaches": {
      "type": "array",
      "maxItems": 20,
      "items": {
        "type": "object",
        "additionalProperties": false,
        "required": [
          "source",
          "breachDate",
          "dataTypes"
        ],
        "properties": {
          "source": {
            "type": "string",
            "minLength": 1,
            "maxLength": 200
          },
          "breachDate": {
            "anyOf": [
              {
                "type": "string",
                "format": "date"
              },
              {
                "type": "null"
              }
            ]
          },
          "dataTypes": {
            "type": "array",
            "maxItems": 30,
            "items": {
              "type": "string",
              "minLength": 1,
              "maxLength": 100
            }
          },
          "affectedUsers": {
            "type": "integer",
            "minimum": 0
          }
        }
      }
    },
    "truncated": {
      "type": "boolean"
    }
  },
  "required": [
    "found",
    "breachCount",
    "type",
    "breaches",
    "truncated"
  ],
  "additionalProperties": false
}
🟢leakdata.password_prefix_check(prefix)

Call this only when the current user message supplies a locally computed five-character SHA-1 hash prefix and asks to check it. Never invent a prefix or reuse one from an earlier message. For general questions about password checks, explain local SHA-1 computation and sharing only its first five hexadecimal characters without calling a tool. Never accept a plaintext password or complete hash. Report only the aggregate values actually returned by this call. Results describe a prefix group only. A matching prefix does not establish whether a particular password is exposed. Do not report confirmed password exposure or recommend changing a password based only on this result. An empty group does not prove that a password is safe.

輸入結構描述

{
  "type": "object",
  "properties": {
    "prefix": {
      "type": "string",
      "pattern": "^[0-9A-Fa-f]{5}$",
      "minLength": 5,
      "maxLength": 5,
      "description": "Five-character SHA-1 hash prefix supplied in the current user message. Never infer it from earlier messages."
    }
  },
  "required": [
    "prefix"
  ],
  "additionalProperties": false
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "found": {
      "type": "boolean",
      "description": "Whether any known hashes share this five-character prefix. A match does not establish that a particular password is exposed."
    },
    "candidateHashCount": {
      "type": "integer",
      "minimum": 0,
      "description": "Number of distinct known hashes sharing the prefix, not matches for one specific password."
    },
    "totalOccurrences": {
      "type": "integer",
      "minimum": 0,
      "description": "Total occurrences across all hashes in the prefix group, not an exposure count for one specific password."
    }
  },
  "required": [
    "found",
    "candidateHashCount",
    "totalOccurrences"
  ],
  "additionalProperties": false
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本2 個工具
已驗證未記錄版本2 個工具
已驗證未記錄版本2 個工具