HackerOne MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| H1_USERNAME | Yes | Your HackerOne username used for API authentication. | |
| H1_API_TOKEN | Yes | Your HackerOne API token generated from HackerOne > Settings > API Token. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_reportsB | Search and list your HackerOne reports. Filter by keyword, program, severity, or state. Great for finding past reports to reference when drafting new ones. |
| get_reportA | Get the full details of a specific HackerOne report by ID. Returns title, vulnerability details, impact, severity, CVSS, timestamps, and program info. |
| get_report_with_conversationA | Get a report with its full triage conversation. Useful for understanding what questions triage asked, how you responded, and what led to resolution. Great for learning what works. |
| get_report_activitiesA | Get the activity timeline of a report: comments, state changes, bounty awards, and triage responses. |
| list_programsC | List bug bounty programs you have access to on HackerOne. |
| analyze_report_patternsA | Fetch your recent reports and analyze patterns: most common vulnerability types, severity distribution, resolution rates, and programs. Useful for understanding your hunting profile. |
| get_program_scopeA | Get the in-scope assets for a bug bounty program. Returns asset types, identifiers, bounty eligibility, and severity caps. Useful when drafting reports to pick the correct asset. |
| get_program_weaknessesB | Get the accepted vulnerability/weakness types for a program. Helps frame reports using the right CWE categories the program cares about. |
| get_earningsB | Get your bounty earnings history. Shows amounts, currency, dates, and which programs paid out. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes, such as get_earnings for bounty history and get_program_scope for program assets, but get_report, get_report_activities, and get_report_with_conversation overlap in focusing on report details, which could cause minor confusion in selection. The descriptions help clarify the differences, but the boundaries are not entirely clear.
All tool names follow a consistent verb_noun pattern with snake_case, such as analyze_report_patterns, get_earnings, and list_programs. There are no deviations in naming conventions, making the set predictable and easy to parse for agents.
With 9 tools, the server is well-scoped for managing HackerOne bug bounty activities, covering key areas like program info, reports, and earnings. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool surface provides comprehensive coverage for bug bounty hunters, including program listing, scope and weakness details, report retrieval and search, and earnings tracking. A minor gap exists in lacking tools for creating or submitting new reports, but agents can work around this with the available tools for drafting and referencing.