h1-brain MCP — Casos de uso, Instalar & Demo en vivo

Por qué usarlo

Características clave

hack(handle) generates one-shot attack briefings with scope, patterns, and vectors
Dual databases: personal bounty history + 3,600+ public disclosures
Search your own rewarded reports, program scopes, and attachments
Search across publicly disclosed HackerOne reports for vulnerability patterns
Real-time scope fetching from HackerOne API

Demo en vivo

Cómo se ve en la práctica

h1-brain.replay ▶ listo

0/0

Instalar

Elige tu cliente

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "h1-brain": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/PatrikFehrenbach/h1-brain"
      ]
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "h1-brain": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/PatrikFehrenbach/h1-brain"
      ]
    }
  }
}

Cursor usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "h1-brain": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/PatrikFehrenbach/h1-brain"
      ]
    }
  }
}

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "h1-brain": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/PatrikFehrenbach/h1-brain"
      ]
    }
  }
}

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "h1-brain",
      "command": "TODO",
      "args": [
        "See README: https://github.com/PatrikFehrenbach/h1-brain"
      ]
    }
  ]
}

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

{
  "context_servers": {
    "h1-brain": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/PatrikFehrenbach/h1-brain"
        ]
      }
    }
  }
}

Añádelo a context_servers. Zed recarga en caliente al guardar.

claude mcp add h1-brain -- TODO 'See README: https://github.com/PatrikFehrenbach/h1-brain'

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: h1-brain

Generate an attack briefing for an authorized bug bounty program

👤 Bug bounty hunters working on authorized HackerOne programs ⏱ ~15 min intermediate

Cuándo usarlo: You're starting work on a new bug bounty target and want a strategic overview.

Requisitos previos

HackerOne API token — Generate at hackerone.com/settings/api_token
h1-brain installed and databases populated — Clone, install, run fetch_rewarded_reports to populate personal DB

Flujo

Generate the briefing

hack('target-company') — Generate a full attack briefing for this program.✓ Copiado

→ Comprehensive briefing with scope, known weakness patterns, untouched assets, and suggested attack vectors
Cross-reference with disclosures

Search disclosed reports for this company. What vulnerability types have been found before?✓ Copiado

→ List of disclosed vulnerabilities with types and bounty amounts

Resultado: A strategic attack plan based on historical data and current scope.

Errores comunes

Stale scope data — The tool fetches fresh scope from HackerOne API, but verify on the program page

Analyze your bug bounty track record to find your strengths

👤 Bug bounty hunters optimizing their approach ⏱ ~20 min beginner

Cuándo usarlo: You want to understand which vulnerability types and programs earn you the most bounties.

Requisitos previos

Personal database populated — Run fetch_rewarded_reports to sync your history

Flujo

Review your history

Search my rewarded reports. Group them by vulnerability type and show the total bounty per type.✓ Copiado

→ Breakdown of earnings by vulnerability category
Identify patterns

Which programs am I most successful on? What do they have in common?✓ Copiado

→ Pattern analysis across your most rewarded programs

Resultado: Insight into your strengths to focus future hunting efforts.

Errores comunes

Old reports may not reflect current program scope — Re-fetch program scopes to get current assets

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

h1-brain + filesystem

Save attack briefings and reports to organized files for each program

Generate an attack briefing for target-company and save it as ~/bounty/target-company/briefing.md.✓ Copiado

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar	Coste
hack	handle: str	Generate a comprehensive attack briefing for a HackerOne program	Multiple API calls
search_reports	query?: str	Search your personal rewarded reports	0 (local DB)
search_disclosed_reports	query?: str	Search across 3,600+ public disclosures	0 (local DB)
search_programs	query?: str	Search bug bounty programs	0 (local DB)
fetch_rewarded_reports	none	Sync your HackerOne rewarded reports to local DB	Multiple API calls

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: HackerOne API rate limits apply during sync and scope fetching
Tokens por llamada: 500–3000 tokens per briefing
Monetario: Free — HackerOne API access is free with your account
Consejo: Populate the local databases once, then queries are free and instant. Re-sync periodically.

Seguridad

Permisos, secretos, alcance

Ámbitos mínimos: HackerOne API token with read access

Almacenamiento de credenciales: API token in environment variable or Claude Desktop config

Salida de datos: API calls to HackerOne during sync and scope fetching. Local DB queries have no network calls.

⚠ This tool is designed for authorized security research, CTF competitions, and defensive analysis only. Do not use it against systems you don't own or have written authorization to test.
Only target programs that are active on HackerOne and within their defined scope.
Your HackerOne API token grants access to your account data. Keep it secure.

Resolución de problemas

Errores comunes y soluciones

Empty personal database

Run fetch_rewarded_reports first to populate your local database from HackerOne.

Verificar: Check that h1_data.db file exists and has data

HackerOne API authentication failed

Verify your API token is valid and hasn't expired. Generate a new one at hackerone.com/settings/api_token.

Verificar: curl -H 'Authorization: ...' https://api.hackerone.com/v1/me

hack() returns empty briefing

The program handle may be incorrect. Search for the exact handle on HackerOne's directory.

Verificar: search_programs to find the correct handle

Alternativas

h1-brain vs otros

Alternativa	Cuándo usarla	Contrapartida
hexstrike-ai	You need active security scanning tools rather than HackerOne-specific intelligence	Broader tool coverage but no HackerOne integration or report history

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills