How do I find my HackEDU API Key?

Log in to your HackEDU Admin Dashboard and navigate to the API section. You will be able to generate and copy your unique X-API-Key from there.

Can I track the training progress of a specific team?

Yes! Use the `get_team_progress` tool by providing the unique team ID. The agent will return the completion percentage and status for that team.

What is 'Adaptive Training' in this integration?

Adaptive Training allows you to push real-world vulnerability findings (via `create_issue`) to HackEDU. The platform then automatically assigns relevant security lessons to developers to help them fix and prevent similar issues.

Is HackEDU now part of Security Journey?

Yes, HackEDU was acquired by Security Journey. This integration works with accounts from both brands using the same API infrastructure.

HackEDU (Security Journey) MCP Server for AutoGen 10 tools — connect in under 2 minutes

Name: HackEDU (Security Journey)
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 10 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add HackEDU (Security Journey) as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

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

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="hackedu_security_journey_agent",
            tools=tools,
            system_message=(
                "You help users with HackEDU (Security Journey). "
                "10 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

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 HackEDU (Security Journey) MCP Server

Connect your HackEDU (now part of Security Journey) platform to any AI agent and take full control of your secure coding training workflows through natural conversation.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use HackEDU (Security Journey) tools. Connect 10 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

What you can do

User & Team Management — List all users and teams, retrieve detailed profiles, and check UUIDs for assignments.
Progress Tracking — Monitor individual and team training progress to ensure security compliance across your organization.
Content Insights — Browse the full catalog of available security training modules and lessons.
Vulnerability Integration — Access HackEDU’s vulnerability taxonomy mapped to CWE, CVE, and CAPEC standards.
Adaptive Training — Push issues from bug bounty programs or scanners to trigger personalized training plans for developers.
Reporting — Instantly retrieve summaries of security training health and identifying gaps in developer knowledge.

The HackEDU (Security Journey) MCP Server exposes 10 tools through the Vinkius. Connect it to AutoGen 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 HackEDU (Security Journey) to AutoGen via MCP

Follow these steps to integrate the HackEDU (Security Journey) MCP Server with AutoGen.

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 10 tools from HackEDU (Security Journey) automatically

Why Use AutoGen with the HackEDU (Security Journey) MCP Server

AutoGen provides unique advantages when paired with HackEDU (Security Journey) through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use HackEDU (Security Journey) tools to solve complex tasks

Role-based architecture lets you assign HackEDU (Security Journey) tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive HackEDU (Security Journey) tool calls

Code execution sandbox: AutoGen agents can write and run code that processes HackEDU (Security Journey) tool responses in an isolated environment

HackEDU (Security Journey) + AutoGen Use Cases

Practical scenarios where AutoGen combined with the HackEDU (Security Journey) MCP Server delivers measurable value.

Collaborative analysis: one agent queries HackEDU (Security Journey) while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from HackEDU (Security Journey), a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using HackEDU (Security Journey) data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process HackEDU (Security Journey) responses in a sandboxed execution environment

HackEDU (Security Journey) MCP Tools for AutoGen (10)

These 10 tools become available when you connect HackEDU (Security Journey) to AutoGen via MCP:

create_issue

Create/Push a new vulnerability issue to trigger adaptive training

get_team_progress

Get the training progress for a specific team

get_user

Get detailed information about a specific user

get_user_progress

Get the training progress for a specific user

list_adaptive_training_plans

List adaptive training plans created based on vulnerability findings

list_content

List all available training modules and lessons

list_issues

List vulnerability issues synced from external sources (e.g., Bugcrowd, HackerOne)

list_teams

List all teams configured in HackEDU

list_users

List all users in your HackEDU account

list_vulnerabilities

List HackEDU vulnerability taxonomy (CWE/CVE/CAPEC mapping)

Example Prompts for HackEDU (Security Journey) in AutoGen

Ready-to-use prompts you can give your AutoGen agent to start working with HackEDU (Security Journey) immediately.

"Show me the training progress for Team Alpha."

"List all security lessons related to SQL Injection."

"Create a new security issue for 'BOLA vulnerability found in API' with vulnerability ID 502."

Troubleshooting HackEDU (Security Journey) MCP Server with AutoGen

Common issues when connecting HackEDU (Security Journey) to AutoGen through the Vinkius, and how to resolve them.

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

HackEDU (Security Journey) + AutoGen FAQ

Common questions about integrating HackEDU (Security Journey) MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call HackEDU (Security Journey) tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.