npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@iflow-mcp/sicks3c-hackerone-mcp-server

v1.0.0

Published

MCP server for accessing HackerOne reports in Claude Code

Downloads

18

Readme

HackerOne MCP Server

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) live access to your HackerOne reports, programs, earnings, and scope data via the HackerOne API.

Setup

1. Get your HackerOne API token

Go to HackerOne > Settings > API Token and generate one.

2. Install and build

git clone https://github.com/Sicks3c/hackerone-mcp-server.git
cd hackerone-mcp-server
npm install
npm run build

3. Add to Claude Code

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"
      }
    }
  }
}

4. Verify

claude
> /mcp
# You should see "hackerone" listed with 9 tools

Tools

| Tool | Description | |------|-------------| | search_reports | Search and filter your reports by keyword, program, severity, or state | | get_report | Get full report details by ID (title, vuln info, severity, timestamps) | | 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 bug bounty programs you have access to | | analyze_report_patterns | Analyze your hunting patterns (severity distribution, top programs, weakness types) | | get_program_scope | Get in-scope assets for a program (asset types, bounty eligibility, severity caps) | | get_program_weaknesses | Get accepted CWE/weakness types for a program | | get_earnings | Get your bounty earnings history (amounts, dates, programs) |

Usage Examples

Search reports by program:

Search my reports for the ipc-h1c-aws-tokyo-2026 program

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?

Check program scope before reporting:

What assets are in scope for the uber program?

Track earnings:

Show my recent bounty earnings

Analyze patterns:

Analyze my report patterns — what severity gets resolved most?

How It Works

  • Connects to the HackerOne Hacker API v1 using your personal API token
  • Runs locally over stdio — your credentials never leave your machine
  • Read-only — cannot submit, modify, or delete reports
  • Filtering (program, severity, state, keyword) is done client-side since the hacker API only supports pagination

License

MIT