Skip to main content
Glama
beepboop2025

data-breach-detector

by beepboop2025
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to data-breach-detector

Related Servers

  • Breach Radar by MAASAI-Labs

    Breach Radarofficial

    MAASAI-Labs
    A
    license
    A
    quality
    C
    maintenance
    Enables MCP clients to look up data breaches and leaked passwords, search NVD CVEs and the CISA KEV catalogue, and generate passive attack-surface reports for a domain covering security headers, TLS, email/DNS security, and CT-log subdomains. All checks are read-only and passive, using only public third-party data sources.
    10
    MIT

  • 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
    C
    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
    A
    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
    MIT

  • 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
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation4/5

There is real conceptual overlap between the historical data tools (breach_news, breach_history, check_exposure, breach_timeline all draw on the same disclosure feeds), but the descriptions explicitly route between them (e.g. 'for one specific organization use check_exposure; for all-time history use breach_history'). assess_threat, feed_sources and breach_stats are clearly distinct. An agent could still occasionally pick breach_history when breach_timeline was intended, but boundaries are well signposted.

Naming Consistency4/5

A clear convention holds: a breach_* family for the archive/feed tools (breach_news, breach_history, breach_timeline, breach_stats) and verb_noun pairs for actions (assess_threat, check_exposure, feed_sources). All snake_case, no mixed casing. Minor deviation in that not every tool follows one single pattern.

Tool Count5/5

Seven tools is a tight, well-scoped set for a breach-intelligence domain: discovery, history, entity triage, timeline, aggregates, threat classification and feed health. Each tool earns its place with no obvious redundancy or filler.

Completeness4/5

The surface covers the full analyst lifecycle: discovery (breach_news/history), triage (check_exposure/assess_threat), chronology (breach_timeline), aggregates (breach_stats) and self-diagnostics (feed_sources). Minor gaps exist — no per-disclosure detail lookup by id and no report/export tool — but core workflows are closed.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources