HackerOne MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HACKERONE_API_TOKEN | Yes | Your HackerOne API token | |
| HACKERONE_TIMEOUT_MS | No | Per-request timeout in milliseconds | 20000 |
| HACKERONE_MAX_RETRIES | No | Number of retries for 429/5xx and transient network errors | 2 |
| HACKERONE_API_USERNAME | Yes | Your HackerOne API token identifier (username) | |
| HACKERONE_RETRY_MAX_DELAY_MS | No | Maximum backoff delay in milliseconds | 4000 |
| HACKERONE_RETRY_BASE_DELAY_MS | No | Initial backoff delay in milliseconds | 400 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| h1_get_hacktivityB | Search public Hacktivity reports using Lucene syntax. |
| h1_list_reportsA | List reports owned by the authenticated hacker. |
| h1_get_reportC | Get a report with its relationships. |
| h1_create_reportC | Submit a vulnerability report. |
| h1_get_balanceB | Get the authenticated hacker's payment balance. |
| h1_get_earningsD | List earnings. |
| h1_get_payoutsC | List payouts. |
| h1_list_programsC | List available programs. |
| h1_get_programC | Get program details. |
| h1_get_program_scopesD | List structured scopes. |
| h1_get_scope_exclusionsC | List excluded report categories. |
| h1_get_program_weaknessesC | List accepted weaknesses. |
| h1_list_report_intentsC | List report intents. |
| h1_get_report_intentB | Get a report intent and pipeline status. |
| h1_create_report_intentC | Create an AI-assisted report intent. |
| h1_update_report_intentA | Update an unsubmitted report intent. |
| h1_delete_report_intentA | Permanently delete an unsubmitted report intent. |
| h1_submit_report_intentD | Submit a ready report intent. |
| h1_list_report_intent_attachmentsC | List report intent attachments. |
| h1_upload_report_intent_attachmentsA | Upload local files to an unsubmitted report intent. |
| h1_delete_report_intent_attachmentA | Permanently delete a report intent attachment. |
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 21 tools
Each tool targets a distinct resource and action. Report intents, attachments, programs, financial data, and reports are clearly separated. Even similar financial tools (balance, earnings, payouts) have clear distinctions.
All tools follow the h1_verb_noun pattern with consistent snake_case. The singular/plural usage for attachments is standard (delete one vs list many). The prefix h1_ is applied uniformly.
21 tools is on the higher end for an MCP server, but each tool corresponds to a specific HackerOne API endpoint. While not over-bloated, the count is borderline heavy compared to typical 3-15 tool servers.
The server covers report intents fully (CRUD + submit + attachments), program reads, financial reads, and report creation/listing. However, there is no update or delete operation for submitted reports, which may be a gap for some workflows.