Unofficial MCP server for accessing your HackerOne reports, programs, scope, and earnings from Claude Code
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"hackerone": {
"env": {
"H1_USERNAME": "your-username",
"H1_API_TOKEN": "your-api-token"
},
"args": [
"/path/to/hackerone-mcp-server/dist/index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Disclaimer: This is an unofficial, community-built project. It is not affiliated with, endorsed by, or maintained by HackerOne. "HackerOne" is a trademark of HackerOne, Inc. This project simply integrates with their publicly documented Hacker API.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
An evil MCP server used for redteam testing
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Security-first platform for AI agents. 38 specialized agents, 15 AI-powered extensions, zero-knowledge multi-agent orchestration. SENTINEL WAF, Ed25519 auth, 2.6M grounding facts.
MCP Security Weekly
Get CVE alerts and security updates for Hackerone Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Disclaimer: This is an unofficial, community-built project. It is not affiliated with, endorsed by, or maintained by HackerOne. "HackerOne" is a trademark of HackerOne, Inc. This project simply integrates with their publicly documented Hacker API.
MCP server that gives Claude Code (or any MCP client) full access to your HackerOne reports, programs, earnings, and scope data via the HackerOne API — including submitting reports and responding to triage.
Go to HackerOne > Settings > API Token and generate one.
git clone https://github.com/Sicks3c/hackerone-mcp-server.git
cd hackerone-mcp-server
npm install
npm run build
claude mcp add hackerone \
-e H1_USERNAME=your-username \
-e H1_API_TOKEN=your-api-token \
-s user \
-- node /path/to/hackerone-mcp-server/dist/index.js
Or add manually to ~/.claude.json:
{
"mcpServers": {
"hackerone": {
"command": "node",
"args": ["/path/to/hackerone-mcp-server/dist/index.js"],
"env": {
"H1_USERNAME": "your-username",
"H1_API_TOKEN": "your-api-token"
}
}
}
}
claude
> /mcp
# You should see "hackerone" listed with 16 tools
| Tool | Description |
|---|---|
search_reports | Search and filter your reports by keyword, program, severity, or state |
get_report | Get full report details including CVSS vector, bounty amounts, and attachments |
get_report_with_conversation | Get a report with its triage conversation thread |
get_report_activities | Get activity timeline (comments, state changes, bounties) |
list_programs | List all bug bounty programs you have access to (auto-paginates) |
get_program_details | Get single program info: policy, response times, metrics |
get_program_scope | Get all in-scope assets for a program (auto-paginates) |
get_program_weaknesses | Get accepted CWE/weakness types for a program (auto-paginates) |
get_earnings | Get your bounty earnings history (amounts, dates, programs) |
get_hacker_profile | Get your reputation, signal, impact, and rank |
get_balance | Get your current unpaid bounty balance |
analyze_report_patterns | Analyze your hunting patterns (severity distribution, top programs, weakness types) |
search_disclosed_reports | Search publicly disclosed reports on hacktivity — great for recon and learning |
| Tool | Description |
|---|---|
submit_report | Submit a new vulnerability report to a program |
add_comment | Add a comment to an existing report (respond to triage) |
close_report | Withdraw/close one of your own reports |
Submit a report directly:
Submit this SSRF finding to the uber program with critical severity. Here's my writeup: [paste]
Respond to triage:
Add a comment to report #2345678: "Here's the updated PoC with the new endpoint..."
Draft a report matching your style:
Find my resolved critical reports and use the same structure to draft a new report for this SSRF I found.
Learn from triage conversations:
Show me the triage conversation on report #2345678. What questions did they ask?
Research what gets paid:
Search disclosed reports on the uber program for SSRF — what did they pay?
Check program details before hunting:
Show me the uber program details — what are their response times?
Check your stats:
Show my hacker profile — what's my current reputation and signal?
Track earnings:
Show my recent bounty earnings and current balance
Analyze patterns:
Analyze my report patterns — what severity gets resolved most?