Skip to main content
Glama

Targets MCP — HackerOne module (read-only)

Custom HackerOne MCP server: 25 tools, all hackerone_*. No database, no cache files, no write actions. Future home of Bugcrowd + other platforms (same tool shape).

Tools

My reports: search_reports, get_report, get_report_with_conversation, get_report_activities, analyze_report_patterns Programs: list_programs, search_programs, get_program_details (categorized + sections subset), get_program_scope, search_scopes, list_scope_exclusions, get_program_weaknesses, list_hacker_invitations Money: get_earnings, list_payouts, get_balance, get_hacker_profile Public: search_disclosed_reports, hack_brief, download_attachment Owner reads (need program-owner token): program_balance, program_bounty_table, program_audit_log, list_program_members Hatch: api_get (GET-only)

Related MCP server: h1-brain

Install

npm install
bash build.sh

Configure (Hermes example)

mcp_servers:
  hackerone:
    command: "node"
    args: ["/home/youssef/tools/hackerone/dist/index.js"]
    env:
      H1_USERNAME: "<api-identifier>"
      H1_API_TOKEN: "<token>"

HackerOne token: https://hackerone.com/settings/api_token/edit

Rules

  • Edit src/ → run build.sh (clients execute dist/, edits alone never load).

  • After rebuild, restart the MCP client session (old sessions keep the old server process).

  • Test: H1_USERNAME=... H1_API_TOKEN=... node tests/verify-mcp.mjs (expect SUITE_PASS).

See docs/ for full details and reference notes.

Available Tools

25 tools
hackerone_analyze_report_patternsA

Analyze your recent reports: severity/state distribution, top programs and weakness types.

Inputs: page_size.

hackerone_api_getA

Raw GET to any HackerOne API path (e.g. /hackers/programs). Read-only by design; use only when no purpose-built tool exists.

Inputs: path (required), params.

hackerone_download_attachmentA

Download a report attachment to tools/hackerone/downloads/ (25MB cap). Returns the file path.

Inputs: report_id (required), attachment_id.

hackerone_get_balanceB

Your current unpaid bounty balance.

Inputs: no named parameters.

hackerone_get_earningsC

Your bounty earnings history: amounts, currency, dates, programs.

Inputs: page_size.

hackerone_get_hacker_profileB

Your profile: username, reputation/signal/impact plus stats computed from your own reports.

Inputs: no named parameters.

hackerone_get_program_detailsA

Full program data in categories: identity, timeline (open date), bounty, metrics (response times), trust, my_stats, policy, scope_summary. Pass sections for only what you need.

Inputs: program_handle (required), sections.

hackerone_get_program_scopeA

In-scope assets of a program. Auto-paginates. Shows types, bounty eligibility, severity caps.

Inputs: program_handle (required), page_size.

hackerone_get_program_weaknessesB

Accepted weakness/CWE types of a program. Auto-paginates.

Inputs: program_handle (required), page_size.

hackerone_get_reportB

Full details of one of your reports: title, vuln info, impact, severity, CVSS, bounty, attachments, program.

Inputs: report_id (required).

hackerone_get_report_activitiesA

Activity timeline of a report: comments, state changes, bounty awards, triage responses.

Inputs: report_id (required), page_size.

hackerone_get_report_with_conversationA

A report with its full triage conversation. Shows what triage asked and what led to resolution.

Inputs: report_id (required).

hackerone_hack_briefA

Attack briefing for a program, all live: bounty scope, your past findings, untouched assets, suggested vectors, public disclosures sample.

Inputs: program_handle (required).

hackerone_list_hacker_invitationsB

Private-invite programs for an account (program-owner API; 403 on plain hacker token).

Inputs: program (required).

hackerone_list_payoutsC

Your payout transactions (provider, status, amounts).

Inputs: page_size.

hackerone_list_program_membersC

Program team members (program-owner API).

Inputs: program (required), page_size.

hackerone_list_programsB

List bug bounty programs you can access. Auto-paginates.

Inputs: page_size.

hackerone_list_scope_exclusionsC

What a program explicitly excludes from scope.

Inputs: program_handle (required).

hackerone_program_audit_logC

Program audit log (program-owner API).

Inputs: program (required), page_size.

hackerone_program_balanceC

Program bounty wallet (program-owner API).

Inputs: program (required).

hackerone_program_bounty_tableC

Program bounty table (program-owner API).

Inputs: program (required).

hackerone_search_disclosed_reportsA

Search public hacktivity. Program filter is exact match. Keyword matches title/weakness/program/reporter, but most items are undisclosed (no titles) so keyword is often empty — browse or filter by program instead.

Inputs: query, program, page_size.

hackerone_search_programsB

Search programs by handle/name, optionally bounty-only. Live, no cache.

Inputs: limit, query, bounty_only.

hackerone_search_reportsC

Search and list your HackerOne reports. Filter by keyword, program, severity, or state.

Inputs: sort, query, state, program, +3 more.

hackerone_search_scopesA

Search in-scope assets by program and/or asset substring, optionally bounty-only. Asset without program matches program names first (empty = no match, pass program_handle).

Inputs: asset, limit, program, bounty_only.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 25 tools

    Disambiguation4/5

    Each tool maps to a specific HackerOne resource/action (report details vs conversation vs activity vs earnings), so misselection risk is low. The only mild ambiguity is the catch-all hackerone_api_get, which overlaps with any existing endpoint, though the description explicitly reserves it for gaps.

    Naming Consistency4/5

    All tools use the hackerone_ prefix and snake_case, with a dominant verb_noun pattern (get_, list_, search_, download_). A few program-owner tools (program_balance, program_bounty_table, program_audit_log) and hack_brief break the verb-first pattern, but the convention is still highly predictable.

    Tool Count3/5

    At 25 tools this is at the heavy end of the 16-25 range. Each tool appears purposeful, but the surface is large and could overwhelm an agent selecting from it.

    Completeness3/5

    The read/analysis side is thorough: reports, programs, scope, earnings, payouts, and admin tools are covered. However, write actions are missing — there is no way to create/update reports, reply in conversations, or otherwise mutate state, and hackerone_api_get is read-only, leaving some workflows dead-ended.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • 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
      Not graded
      quality
      Not graded
      maintenance
      Connects Claude to the HackerOne Hacker API, enabling program listing, scope retrieval, report management, and balance checks via natural language.
      6
      -
    • 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
      -