Targets MCP
# 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)
## Install
```bash
npm install
bash build.sh
```
## Configure (Hermes example)
```yaml
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.
TDQS
Scored across 25 tools
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.
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.
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.
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.