How do I generate my HackerOne API Token?

Log in to HackerOne, navigate to **Settings > API Token**, and click 'Create API Token'. Make sure to copy both the **Identifier** and the **Token Value** immediately.

Can I award bounties through this integration?

Yes! Use the `award_bounty` tool by providing the report ID and the amount. You can also specify an optional bonus amount for the researcher.

Does the integration support internal comments?

Yes, the `add_report_comment` tool has an optional `internal` boolean parameter (defaults to true). This allows you to communicate with your team privately on a specific report.

Can I filter reports by their handle or ID?

You can use `list_reports` to see all reports or `get_report` with a specific ID to retrieve detailed information for a single discovery.

HackerOne MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: HackerOne
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to HackerOne through Vinkius, pass the Edge URL in the `mcps` parameter and every HackerOne tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="HackerOne Specialist",
    goal="Help users interact with HackerOne effectively",
    backstory=(
        "You are an expert at leveraging HackerOne tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in HackerOne "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About HackerOne MCP Server

Connect your HackerOne organization account to any AI agent and take full control of your vulnerability management workflows through natural conversation.

When paired with CrewAI, HackerOne becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HackerOne tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Report Oversight — List all vulnerability reports, retrieve detailed information, and monitor their current state and severity.
Program Insights — Browse your bug bounty or VDP programs and access structured scopes and assets.
Report Interaction — Add comments to reports, change their triaged state, or award bounties directly from the chat.
Asset Tracking — Monitor the assets defined within your security programs and their reachability.
Financial Monitoring — Retrieve history of bounty payments and manage rewards efficiently.
Hacktivity Feed — Stay updated with the internal or public hacktivity feed to see recent discoveries.

The HackerOne MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect HackerOne to CrewAI via MCP

Follow these steps to integrate the HackerOne MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from HackerOne

Why Use CrewAI with the HackerOne MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with HackerOne through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

HackerOne + CrewAI Use Cases

Practical scenarios where CrewAI combined with the HackerOne MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries HackerOne for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries HackerOne, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain HackerOne tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries HackerOne against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

HackerOne MCP Tools for CrewAI (10)

These 10 tools become available when you connect HackerOne to CrewAI via MCP:

add_report_comment

Add a comment to a specific vulnerability report

award_bounty

Award a bounty for a vulnerability report

change_report_state

Update the state of a vulnerability report (e.g., triaged, resolved)

get_program

Get details for a specific security program

get_report

Get detailed information about a specific vulnerability report

list_assets

List assets defined in your security programs

list_hacktivity

List the HackerOne hacktivity feed

list_payments

List bounty payments history

list_programs

List bug bounty or VDP programs you have access to

list_reports

List vulnerability reports submitted to your HackerOne program

Example Prompts for HackerOne in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with HackerOne immediately.

"List all vulnerability reports submitted this week."

"Award a $500 bounty to report ID 12345."

"Change the state of report 12345 to 'Triaged'."

Troubleshooting HackerOne MCP Server with CrewAI

Common issues when connecting HackerOne to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

HackerOne + CrewAI FAQ

Common questions about integrating HackerOne MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.