CyberSecurityLab MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@CyberSecurityLab MCP ServerCheck the reputation of IP 185.220.101.5."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cybersecurity MCP Learning Laboratory
This repository is a progressive learning and experimentation laboratory for:
Model Context Protocol (MCP)
Building cybersecurity MCP servers
Studying MCP security
Experimenting with AI-assisted software development
Repository Structure
The repository is organized as a monorepo of independent learning laboratories (labs). Each lab is a self-contained OpenCode workspace with its own:
Virtual environment (
.venv)Dependencies (
requirements.txt)OpenCode configuration (
opencode.json)MCP server implementation
Labs are located in the labs/ directory and are numbered sequentially to reflect the learning progression.
Related MCP server: Vulnerable MCP Server
Lab Index
Lab | Directory | Status | Description |
Lab 01 |
| ✅ Completed and validated | Basic MCP server with simulated threat intelligence: |
Lab 02 |
| ✅ Completed and validated | MCP server wrapping the AbuseIPDB API: |
Lab 03 |
| ✅ Implemented | MCP server exposing multiple cybersecurity tools: |
Lab 04 |
| ✅ Completed and validated | MCP server demonstrating dynamic MCP Resources: static resources ( |
Lab 05 |
| ✅ Completed and validated | MCP server providing a controlled read-only abstraction layer over a simulated SIEM dataset. Resources: |
Lab 06 |
| ✅ Completed and validated | Multi-MCP server demonstrating autonomous tool selection across cyber-siem and cyber-ti, evidence fusion, and LLM inference with strict read-only access. |
Lab 07 |
| ✅ Completed and validated | Identity and authorization lab: MCP server enforced authorization server-side; tested alice (events:read) allowed search_events, bob denied; carol (summary:read) allowed get_security_summary, alice denied; unknown identities denied UNKNOWN_IDENTITY; prompt-based authorization bypass attempts failed with ACCESS_DENIED; observed identity-binding limitation where claimed identity influenced authorization; documented security principles and architectural lessons. |
Lab 08 |
| ✅ Completed and validated | Authentication and identity binding: MCP server authenticates via CYBERLAB_TOKEN, derives identity server-side, enforces authorization post-authentication, default deny, read-only capabilities. |
Lab 09 |
| ✅ Completed and validated | High-Impact Tools, Human-in-the-Loop and Excessive Agency |
Lab 10 |
| ✅ Implemented and validated | Secure multi-MCP agentic SOC lab with three MCP servers: cyber-soc, cyber-ti, cyber-response. End-to-end workflow: Incident → SOC evidence → Threat Intelligence → correlation/reasoning → proposal → human approval → execution → independent verification. |
All labs 01 through 10 have been implemented and validated.
Setup Instructions
Clone the repository
Navigate to a lab directory (e.g.,
cd labs/lab01-basic-mcp)Install dependencies:
pip install -r requirements.txtConfigure environment variables if required (see lab-specific README)
Launch OpenCode from the lab directory to access the MCP server
Note: Each lab is an independent OpenCode workspace. You must launch OpenCode from within the lab directory to use its configured MCP server.
Security Focus
This laboratory emphasizes secure MCP practices:
Secrets (e.g., API keys) are kept outside version control using
.envfilesInternal exceptions are not exposed to the LLM; sanitized error messages are returned
Tool descriptions and contracts are carefully crafted to influence correct tool selection by the model
Input validation and response normalization prevent injection attacks
Each lab builds on previous lessons to progressively introduce security considerations
See ROADMAP.md for the planned learning progression.
This server cannot be deployed
Maintenance
Related MCP Connectors
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Cybersecurity MCP server for URL scanning, threat intelligence, and domain reputation.
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
MCP server for innovationlab documentation, generated by doc2mcp.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA remote MCP server that exposes mock application security testing data (applications, scans, issues) for LLM clients to query security posture using natural language.-
- FlicenseNot gradedqualityDmaintenanceA deliberately insecure MCP server designed as a pentest lab to demonstrate common vulnerabilities in MCP deployments.-
- AlicenseNot gradedqualityDmaintenanceMCP server that provides programmatic access to the SOLVE-IT digital forensics knowledge base, enabling LLMs to query, navigate, and search forensic techniques, weaknesses, mitigations, objectives, and citations.2MIT
- AlicenseCqualityCmaintenanceAn educational MCP server exposing shell command execution (PowerShell and sh) and a benign tool for learning about MCP tools, resources, and security risks like tool poisoning.33MIT