Skip to main content
Glama
beepboop2025

data-breach-detector

by beepboop2025
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to data-breach-detector

No user-submitted related servers found.

    Related Servers

    • mcp-threatintel

      pete-builds
      A
      license
      Not graded
      quality
      A
      maintenance
      A threat intelligence MCP server for Claude Code that enables lookup of IOCs, threat feeds, breached credentials, CVEs, and dark web data.
      2
      MIT

    • Have I Been Pwned MCP Server

      Cyreslab-AI
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides integration with the Have I Been Pwned API to check if your accounts or passwords have been compromised in data breaches.
      4
      2
      MIT

    • mcp-osint

      DanDaDaDanDan
      F
      license
      A
      quality
      D
      maintenance
      MCP server that provides access to 14 OSINT data sources including government, research, corporate, and news APIs, enabling search, preview, and retrieval of public intelligence data.
      4
      -

    • tweetfeed-mcp

      0xDanielLopez
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing tweetfeed.live's IOC feed (URLs, domains, IPs, hashes) as tools for querying threat intelligence, with checks, enrichment, trends, and campaign clustering.
      MIT

    • mailtype-api

      GSterlingPress
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for inspecting email domains and addresses, providing objective domain-level email infrastructure answers such as MX, SPF, DMARC, MTA-STS, and disposable-domain evidence.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 7 tools

    Disambiguation4/5

    Tools are mostly mapped to distinct output contracts: single-entity summary vs single-entity chronology vs searchable history vs recent news vs aggregate stats vs text triage vs feed health. The main ambiguity is between check_exposure and breach_timeline (both target one entity) and between breach_news and breach_history (recent vs full archive), but cross-references in the descriptions make misselection unlikely.

    Naming Consistency3/5

    All names are readable snake_case, but the convention is mixed: four tools use the noun-prefix pattern breach_timeline/breach_news/breach_history/breach_stats, while assess_threat and check_exposure use verb_noun and feed_sources is a noun-noun phrase. There is no uniform verb_noun scheme, though the breach_ prefix creates some predictability.

    Tool Count5/5

    Seven tools is well within the ideal range for this domain. Each tool earns its place by covering a different analyst workflow—entity lookups, historical search, recent news, statistics, feed transparency, and local text classification—without filler or redundant duplicates.

    Completeness5/5

    The surface fully covers the read-only public-breach research domain: exposure presence, incident chronology, filterable full-history search, recent disclosures, aggregate statistics, source staleness checks, and ad-hoc text triage. No obvious dead ends exist, and write operations are not expected for this metadata-only disclosure tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources