Skip to main content
Glama

Related Servers

Alternatives to vulns-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to HackerOne to pull bug bounty history, program scopes, and report details into a local SQLite database, exposing tools for searching, analyzing, and generating attack briefings using both personal and public disclosed reports.
      360
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Provides read-only access to HackerOne reports, program scopes, and bounty earnings through the HackerOne API. It enables users to analyze hunting patterns, check asset eligibility, and retrieve report details or triage conversations via natural language.
      9
      43
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to HackerOne bug bounty history, program scopes, and public disclosed reports for searching, analyzing, and generating attack briefings.
      MIT
    • F
      license
      B
      quality
      C
      maintenance
      Enables read-only interaction with HackerOne, providing tools for searching and analyzing reports, exploring programs and scope, accessing earnings, and retrieving public disclosures.
      25
      -
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with HackerOne for managing reports, checking program scope, analyzing earnings, and more through natural language commands.
      28
      -

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: list_categories enumerates bug classes, get_category_guide explains one, search_reports finds prior art, get_report fetches a full write-up, find_similar pivots from one report, get_program profiles a target, and archive_stats summarizes the corpus. Overlap between list_categories and get_category_guide is minimal and the descriptions make the boundary clear.

    Naming Consistency4/5

    Most names follow a readable verb_noun pattern (get_category_guide, get_program, search_reports, get_report, find_similar, list_categories). The only deviation is archive_stats, which is noun-only, but the set remains predictable overall.

    Tool Count5/5

    Seven tools is well-scoped for a vulnerability-report archive server. Each tool covers a distinct research workflow step: discovery, browsing, deep-dive, cross-referencing, and contextual guidance.

    Completeness4/5

    The surface covers the core research lifecycle: list categories, search reports, read full reports, find similar reports, view program history, and get category playbooks. Minor gaps exist, such as no direct tool to enumerate or search programs or researchers, but agents can work around these via search_reports and archive_stats.