Bug Bounty Platform MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| H1_API_KEY | No | Your HackerOne API token (used with H1_USERNAME for Basic Auth). Optional; only needed for HackerOne integration. | |
| H1_USERNAME | No | Your HackerOne username (used with H1_API_KEY for Basic Auth). Optional; only needed for HackerOne integration. | |
| YWH_API_TOKEN | No | Your YesWeHack personal access token (Bearer Auth). Optional; only needed for YesWeHack integration. | |
| INTIGRITI_API_TOKEN | No | Your Intigriti Researcher API token (Bearer Auth). Optional; only needed for Intigriti integration. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bounty_get_platforms_statusA | Check the credential and operational status of all supported platforms (HackerOne, YesWeHack, Intigriti). Returns which platforms are currently configured and which environment variables are missing. |
| bounty_search_programsA | Search and filter bug bounty programs across HackerOne, YesWeHack, and Intigriti. Args: query: Search keyword to filter program handle or name (e.g. 'google', 'uber', 'crypto'). platform: Platform to search ('all', 'hackerone', 'yeswehack', or 'intigriti'). Defaults to 'all'. bbp_only: If True, only returns programs offering monetary rewards (Bug Bounty Programs). public_only: If True, only returns publicly accessible programs. |
| bounty_get_programB | Retrieve full details, guidelines, policy, and scope for a specific program. Args: platform: Platform name ('hackerone', 'yeswehack', or 'intigriti'). identifier: Program handle (HackerOne), slug (YesWeHack), or ID (Intigriti). |
| bounty_get_scopeA | Retrieve all structured scope items (in-scope and out-of-scope) for a specific program. Args: platform: Platform name ('hackerone', 'yeswehack', or 'intigriti'). identifier: Program identifier. include_oos: Whether to include explicitly declared out-of-scope assets. Defaults to True. |
| bounty_check_targetA | Verify whether a target domain, IP, CIDR subnet, or URL is in-scope across bug bounty programs. Evaluates wildcards (*.target.com), IP ranges, and path prefixes. Args: target: The target asset to check (e.g. 'api.example.com', '192.168.1.10', 'https://example.com/v1'). platform: Platform to inspect ('all', 'hackerone', 'yeswehack', or 'intigriti'). Defaults to 'all'. |
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 5 tools
Each tool targets a distinct action (search, get details, get scope, check target, platform status), but there is minor overlap between bounty_get_program (which includes scope) and bounty_get_scope (structured scope only). The descriptions clarify the difference, so agents can reliably choose correctly.
All tool names share the 'bounty_' prefix and follow a consistent verb_noun pattern: search_programs, get_program, get_scope, check_target, get_platforms_status. This makes the API predictable and easy to navigate.
Five tools is well-scoped for this read-only bug bounty program intelligence server. Each tool has a clearly necessary role—searching, retrieving program details, fetching structured scope, verifying targets, and checking platform connectivity—no unnecessary bloat or missing critical operations.
The core workflows of discovering and assessing bug bounty programs are well covered: searching programs, reading full policies, inspecting scope, checking target eligibility, and monitoring platform status. Minor gaps include the lack of a dedicated 'list all programs' endpoint, though this can be achieved via an empty search query, and the server intentionally omits submission or hunting features, which appear outside its scope.