Skip to main content
Glama
Miro-sh

yeswehack-mcp

by Miro-sh

Related Servers

Alternatives to yeswehack-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables read-only access to HackerOne Hacker API data including program policies, structured scopes, scope exclusions, hacktivity/prior art, and your own reports through MCP clients.
      8
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that lets an agent browse the HackerOne Hacker API using an authenticated hacker account, exposing programs, policies, scope, reports, and payments. It cannot create, update, or submit reports.
      15
      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
      -
    • A
      license
      A
      quality
      A
      maintenance
      Lets MCP clients browse bug bounty programmes, manage reports, and triage issues on BugSecure with user-approved OAuth permissions, including read-only mode.
      33
      273 npm
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables reading EBP Cloud/SaaS business data (Hubbix Comptabilité, Hubbix Gestion Commerciale, SaaS Gestion Commerciale, SaaS Bâtiment) through a set of read-only business tools over stdio, using user-supplied EBP credentials. Note that data exposed to the MCP client may be transmitted to whichever model provider it uses.
      MIT

    TDQS

    A3.5/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target a distinct resource+action pair: programs, reports, credits, and scope checking are clearly separated. The program-related tools (list_accessible_programs, search_programs, recently_updated_programs, compare_programs) have subtle differences, but the descriptions provide enough clarity to avoid serious misselection.

    Naming Consistency4/5

    The vast majority of tools follow a snake_case verb_noun pattern like list_my_reports, get_program, search_programs, and compare_programs. A few exceptions such as session_status, my_report_status_counts, my_hunter_dashboard, and recently_updated_programs break the verb-first style, but the overall naming remains predictable and readable.

    Tool Count4/5

    18 tools is on the heavier side but still reasonable for a bug bounty platform covering authentication, programs, reports, credits, scope validation, and program activity. Each tool addresses a distinct need and none feels redundant enough to remove.

    Completeness3/5

    The read-only reconnaissance and monitoring surface is well covered: programs, reports, scopes, credits, activity, and rankings are all present. However, there are no mutation tools at all, such as submitting or updating a report, which leaves the server unable to support a full end-to-end hunter workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues